Certificate Authority Settings

Certificate Authority Settings

Secure Home | Search | About
 Microsoft Applications Security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
Certificate Authority Settings sihfmis 05-22-2007
Posted by =?Utf-8?B?c2loZm1pcw==?= on May 22, 2007, 3:46 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
What is the typical naming convention when setting up the name field within
Certificate Authority? I have read a couple articles that inticate the name
should be the same as the company's web site name. ??? I am not sure if
that is what I want to do. Is it a logical call that CA uses? HELP!!!

Posted by S. Pidgorny on May 23, 2007, 5:20 am
If you were  Registered and logged in, you could reply and use other advanced thread options
I assume your question is about Web server SSL certificates. The name field
(certificate subject) should match fully-qualified domain name of the
server, as it is used by the users. I'll give you and example - go to the
following two Web sites:

https://www.verisign.com
https://verisign.com

Both are one and the same, serving same content from the same servers. The
difference is that you'll get a certificate warning accessing the latter,
because the certificate is for www.verisign.com

Similar principle applies to other certificate types

--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-

* http://sl.mvps.org * http://msmvps.com/blogs/sp *

> What is the typical naming convention when setting up the name field
> within
> Certificate Authority? I have read a couple articles that inticate the
> name
> should be the same as the company's web site name. ??? I am not sure if
> that is what I want to do. Is it a logical call that CA uses? HELP!!!



Posted by =?Utf-8?B?c2loZm1pcw==?= on May 23, 2007, 9:20 am
If you were  Registered and logged in, you could reply and use other advanced thread options
Okay, just to make sure I am on the same page as you, let me give a brief
explanation of what I am doing. I am configuring my Exchange server to use
OWA with certificate verification. Do I still give the name field the
fully-qualified domain name or can I give it whatever?

"S. Pidgorny <MVP>" wrote:

> I assume your question is about Web server SSL certificates. The name field
> (certificate subject) should match fully-qualified domain name of the
> server, as it is used by the users. I'll give you and example - go to the
> following two Web sites:
>
> https://www.verisign.com
> https://verisign.com
>
> Both are one and the same, serving same content from the same servers. The
> difference is that you'll get a certificate warning accessing the latter,
> because the certificate is for www.verisign.com
>
> Similar principle applies to other certificate types
>
> --
> Svyatoslav Pidgorny, MS MVP - Security, MCSE
> -= F1 is the key =-
>
> * http://sl.mvps.org * http://msmvps.com/blogs/sp *
>
> > What is the typical naming convention when setting up the name field
> > within
> > Certificate Authority? I have read a couple articles that inticate the
> > name
> > should be the same as the company's web site name. ??? I am not sure if
> > that is what I want to do. Is it a logical call that CA uses? HELP!!!
>
>
>

Posted by Brian Komar on May 23, 2007, 7:18 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
On Wed, 23 May 2007 06:20:01 -0700, sihfmis wrote:

> Okay, just to make sure I am on the same page as you, let me give a brief
> explanation of what I am doing. I am configuring my Exchange server to use
> OWA with certificate verification. Do I still give the name field the
> fully-qualified domain name or can I give it whatever?
>
> "S. Pidgorny <MVP>" wrote:
>
>> I assume your question is about Web server SSL certificates. The name field
>> (certificate subject) should match fully-qualified domain name of the
>> server, as it is used by the users. I'll give you and example - go to the
>> following two Web sites:
>>
>> https://www.verisign.com
>> https://verisign.com
>>
>> Both are one and the same, serving same content from the same servers. The
>> difference is that you'll get a certificate warning accessing the latter,
>> because the certificate is for www.verisign.com
>>
>> Similar principle applies to other certificate types
>>
>> --
>> Svyatoslav Pidgorny, MS MVP - Security, MCSE
>> -= F1 is the key =-
>>
>> * http://sl.mvps.org * http://msmvps.com/blogs/sp *
>>
>>> What is the typical naming convention when setting up the name field
>>> within
>>> Certificate Authority? I have read a couple articles that inticate the
>>> name
>>> should be the same as the company's web site name. ??? I am not sure if
>>> that is what I want to do. Is it a logical call that CA uses? HELP!!!
>>
>>
>>

If you want errors when you connect, just type in whatever you want. If you
want no errors, then make the subject = the DNS name that users will type
to connect to the OWA sight <G>
Brian

Similar ThreadsPosted
what type of certificate authority? June 16, 2005, 4:08 pm
Certificate Authority type June 16, 2005, 6:01 pm
Problem with certificate authority January 27, 2006, 9:03 am
Certificate Authority (CA) - Failover Possible? February 24, 2006, 8:20 pm
Microsoft Certificate Authority June 14, 2006, 8:25 am
Problem in Certificate Authority February 23, 2007, 4:09 am
Certificate Authority Configuration February 25, 2008, 11:47 pm
Re: Certificate Authority services on W2k forest June 14, 2005, 4:23 pm
Renaming a Certificate Root authority June 28, 2006, 5:16 pm
Local Certificate Authority Server July 7, 2006, 1:53 am

The site map in XML format XML site map

Contact Us | Privacy Policy