Re: Delivering certificate not in the same domain name ?
- From: "neo [mvp outlook]" <neo@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 3 Apr 2008 16:32:51 -0700
Yes, you can issue certificates for other domain names other than
"mycompany.local".
Correct, if issuing self-signed certificates then a copy of the CA
certificate has to be installed on non-domain member workstations and
servers. (Member workstation/servers automatically get a copy installed at
the time of joining the active directory domain.) Once this is done, no
more prompts because a certificate can be verified back to the CA
certificate.
"Pascal" <pascal_t@xxxxxxxxxxxxxxxxxx> wrote in message
news:mn.13097d848c1e7cbc.70874@xxxxxxxxxxxxxxxxxxxxx
Hello,
another question ;-)
If I am installing an enterprise Windows certificate authority, the
delivered certificates have to be delievered only for the same domain name
as my active directory domain name ?
For example, if my domain is "mycompany.local", does it mean that only
certificates for *.mycompany.local can be delivered or I can deliver a
certificate for "www.mywebsite.com" ?
If I can deliver a certificate for www.mywebsite.com and I install the
root certificate of my enterprise CA in the client computer, this computer
will not have any warning message, so ?
Thank you
--
Pascal
.
- Follow-Ups:
- References:
- Delivering certificate not in the same domain name ?
- From: Pascal
- Delivering certificate not in the same domain name ?
- Prev by Date: domain access control for local user of domain computer?
- Next by Date: Re: Delivering certificate not in the same domain name ?
- Previous by thread: Delivering certificate not in the same domain name ?
- Next by thread: Re: Delivering certificate not in the same domain name ?
- Index(es):
Relevant Pages
|
