Need Cert to work with and without WWW.

am 08.10.2007 23:44:03 von Danno

Hi,

I have seen some reference to a Wildcard certificate that allows you to
secure subdomains such as www.domain.com. Is this correct that a wildcard
cert will not secure the parent domain?

What I really need to know is how to get this cert I purchased for
domain.com to not generate any warnings when a user visit www.domain.com.

Thank you,

Re: Need Cert to work with and without WWW.

am 09.10.2007 05:10:48 von Bernard

what do you mean by 'will not secure the parent domain'?
if you have *.domain.com the wildcard cert make sense as it share the same
parent domain.
but for domain.com - you would need another cert as it's not sharing the
same common name structure of *.domain.com

--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/

"Danno" wrote in message
news:B916E0B4-7D8D-483B-BBA6-1833DFBA27A3@microsoft.com...
> Hi,
>
> I have seen some reference to a Wildcard certificate that allows you to
> secure subdomains such as www.domain.com. Is this correct that a wildcard
> cert will not secure the parent domain?
>
> What I really need to know is how to get this cert I purchased for
> domain.com to not generate any warnings when a user visit www.domain.com.
>
> Thank you,
>

Re: Need Cert to work with and without WWW.

am 09.10.2007 21:25:02 von Danno

Understood.

So how does one secure a web page whether users type in http://domain.com or
http://www.domain.com?

"Bernard Cheah [MVP]" wrote:

> what do you mean by 'will not secure the parent domain'?
> if you have *.domain.com the wildcard cert make sense as it share the same
> parent domain.
> but for domain.com - you would need another cert as it's not sharing the
> same common name structure of *.domain.com
>
> --
> Regards,
> Bernard Cheah
> http://www.iis.net/
> http://msmvps.com/blogs/bernard/
>
>
> "Danno" wrote in message
> news:B916E0B4-7D8D-483B-BBA6-1833DFBA27A3@microsoft.com...
> > Hi,
> >
> > I have seen some reference to a Wildcard certificate that allows you to
> > secure subdomains such as www.domain.com. Is this correct that a wildcard
> > cert will not secure the parent domain?
> >
> > What I really need to know is how to get this cert I purchased for
> > domain.com to not generate any warnings when a user visit www.domain.com.
> >
> > Thank you,
> >
>
>
>

Re: Need Cert to work with and without WWW.

am 10.10.2007 05:36:41 von Bernard

Two sites, two certs point to the same content path.

--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/

"Danno" wrote in message
news:1B696B45-F53C-41AE-A14F-53294C6BB453@microsoft.com...
> Understood.
>
> So how does one secure a web page whether users type in http://domain.com
> or
> http://www.domain.com?
>
> "Bernard Cheah [MVP]" wrote:
>
>> what do you mean by 'will not secure the parent domain'?
>> if you have *.domain.com the wildcard cert make sense as it share the
>> same
>> parent domain.
>> but for domain.com - you would need another cert as it's not sharing the
>> same common name structure of *.domain.com
>>
>> --
>> Regards,
>> Bernard Cheah
>> http://www.iis.net/
>> http://msmvps.com/blogs/bernard/
>>
>>
>> "Danno" wrote in message
>> news:B916E0B4-7D8D-483B-BBA6-1833DFBA27A3@microsoft.com...
>> > Hi,
>> >
>> > I have seen some reference to a Wildcard certificate that allows you to
>> > secure subdomains such as www.domain.com. Is this correct that a
>> > wildcard
>> > cert will not secure the parent domain?
>> >
>> > What I really need to know is how to get this cert I purchased for
>> > domain.com to not generate any warnings when a user visit
>> > www.domain.com.
>> >
>> > Thank you,
>> >
>>
>>
>>

Re: Need Cert to work with and without WWW.

am 10.10.2007 17:23:02 von Danno

I see. Alternatively, couldn't one redirect traffic from
http://www.domain.com to http://domain.com? I'm not sure how you would do
that in IIS.

Thank you,

"Bernard Cheah [MVP]" wrote:

> Two sites, two certs point to the same content path.
>
> --
> Regards,
> Bernard Cheah
> http://www.iis.net/
> http://msmvps.com/blogs/bernard/
>
>
> "Danno" wrote in message
> news:1B696B45-F53C-41AE-A14F-53294C6BB453@microsoft.com...
> > Understood.
> >
> > So how does one secure a web page whether users type in http://domain.com
> > or
> > http://www.domain.com?
> >
> > "Bernard Cheah [MVP]" wrote:
> >
> >> what do you mean by 'will not secure the parent domain'?
> >> if you have *.domain.com the wildcard cert make sense as it share the
> >> same
> >> parent domain.
> >> but for domain.com - you would need another cert as it's not sharing the
> >> same common name structure of *.domain.com
> >>
> >> --
> >> Regards,
> >> Bernard Cheah
> >> http://www.iis.net/
> >> http://msmvps.com/blogs/bernard/
> >>
> >>
> >> "Danno" wrote in message
> >> news:B916E0B4-7D8D-483B-BBA6-1833DFBA27A3@microsoft.com...
> >> > Hi,
> >> >
> >> > I have seen some reference to a Wildcard certificate that allows you to
> >> > secure subdomains such as www.domain.com. Is this correct that a
> >> > wildcard
> >> > cert will not secure the parent domain?
> >> >
> >> > What I really need to know is how to get this cert I purchased for
> >> > domain.com to not generate any warnings when a user visit
> >> > www.domain.com.
> >> >
> >> > Thank you,
> >> >
> >>
> >>
> >>
>
>
>

Re: Need Cert to work with and without WWW.

am 11.10.2007 04:24:09 von Bernard

Arghh.. well you can do that. i thought you need https for both.
if only one, then of coz, just configure domain.com request to forward to
https www.domain.com
either via IIS MMC or use a default page to response.redirect etc..

--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/

"Danno" wrote in message
news:84F35C84-6857-47AB-B81E-6BCD6B645184@microsoft.com...
>I see. Alternatively, couldn't one redirect traffic from
> http://www.domain.com to http://domain.com? I'm not sure how you would do
> that in IIS.
>
> Thank you,
>
> "Bernard Cheah [MVP]" wrote:
>
>> Two sites, two certs point to the same content path.
>>
>> --
>> Regards,
>> Bernard Cheah
>> http://www.iis.net/
>> http://msmvps.com/blogs/bernard/
>>
>>
>> "Danno" wrote in message
>> news:1B696B45-F53C-41AE-A14F-53294C6BB453@microsoft.com...
>> > Understood.
>> >
>> > So how does one secure a web page whether users type in
>> > http://domain.com
>> > or
>> > http://www.domain.com?
>> >
>> > "Bernard Cheah [MVP]" wrote:
>> >
>> >> what do you mean by 'will not secure the parent domain'?
>> >> if you have *.domain.com the wildcard cert make sense as it share the
>> >> same
>> >> parent domain.
>> >> but for domain.com - you would need another cert as it's not sharing
>> >> the
>> >> same common name structure of *.domain.com
>> >>
>> >> --
>> >> Regards,
>> >> Bernard Cheah
>> >> http://www.iis.net/
>> >> http://msmvps.com/blogs/bernard/
>> >>
>> >>
>> >> "Danno" wrote in message
>> >> news:B916E0B4-7D8D-483B-BBA6-1833DFBA27A3@microsoft.com...
>> >> > Hi,
>> >> >
>> >> > I have seen some reference to a Wildcard certificate that allows you
>> >> > to
>> >> > secure subdomains such as www.domain.com. Is this correct that a
>> >> > wildcard
>> >> > cert will not secure the parent domain?
>> >> >
>> >> > What I really need to know is how to get this cert I purchased for
>> >> > domain.com to not generate any warnings when a user visit
>> >> > www.domain.com.
>> >> >
>> >> > Thank you,
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>