Domain authentication with FQDN in the URL

Hello,

I have a little problem with domain authentication on my SharePoint.
When I use my address https://computer/my_site/ , every client on my domain
can access the website without having to put its login & password. The
inconvenient is that my SSL certificate is for https://computer.mydomain/ so,
I have a little warning….
So when I use the URL https://computer/mydomain/my_site , I don’t have the
warning for the certificate, but I have to login manually with my login &
password from the domain 

Would you have any idea for not having any of these issues ?

Thanks in advance,
Regards,

Vincent
VincentD [ Mi, 10 Januar 2007 16:02 ] [ ID #1591065 ]

Re: Domain authentication with FQDN in the URL

Vincent wrote on Wed, 10 Jan 2007 07:02:00 -0800:

> Hello,
>
> I have a little problem with domain authentication on my SharePoint.
> When I use my address https://computer/my_site/ , every client on my
> domain
> can access the website without having to put its login & password. The
> inconvenient is that my SSL certificate is for https://computer.mydomain/
> so,
> I have a little warning.
> So when I use the URL https://computer/mydomain/my_site , I dont have the
> warning for the certificate, but I have to login manually with my login &
> password from the domain ?
>
> Would you have any idea for not having any of these issues ?

This is a browser issue, not IIS.

However, there are two solutions I can think of.

(1) Replace the certificate with one that has a CN of computer so that it
matches the first URL.

(2) Adjust every client machine so that computer.mydomain is in the Trusted
Sites zone in Internet Explorer - this could be done via GPO for instance,
if they are all pulling policies from a centralised server.

Dan
Daniel Crichton [ Mi, 10 Januar 2007 16:51 ] [ ID #1591066 ]
Webserver » microsoft.public.inetserver.iis.security » Domain authentication with FQDN in the URL

Vorheriges Thema: Client Side Authentication Between Two Servers?
Nächstes Thema: Intranet site not working after losing primary DNS server