Welcome to ISAserver.org

Wildcard cert issue's

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Wildcard cert issue's

Page: [1]

Message

<< Older Topic Newer Topic >>

Wildcard cert issue's - 14.Sep.2004 7:24:00 PM

StarChase

Posts: 59
Joined: 5.Feb.2004
From: The Netrherlands
Status: offline

Hi all,

I now have registred a domain name and maked subdomains like owa.mydomain.nl
Ive implemented the wildcard cert to publish multiple SSL sites, but im running into some minor problems.

1. Is it normal that the client uses/display's *.mydomain.nl cert for all SSL sites?

2. I also have published my owa site, but now it comes back with a dubble logon and seas that also non secure items are present in my owa site, what im i doing wrong, is this normal?

Thanxz

[ September 14, 2004, 07:26 PM: Message edited by: StarChase ]

Post #: 1

Featured Links*

RE: Wildcard cert issue's - 15.Sep.2004 4:08:00 AM

tshinder

Posts: 47669
Joined: 10.Jan.2001
From: Texas
Status: online

Hi Star,

The wildcard cert will not cause double logon prompts, so something else is causing that. I'm not sure what you mean by the other problem.

HTH,
Tom

(in reply to StarChase)

Post #: 2

RE: Wildcard cert issue's - 16.Sep.2004 3:01:00 PM

StarChase

Posts: 59
Joined: 5.Feb.2004
From: The Netrherlands
Status: offline

What i mean is that when a external client is on a published SSL site and goes to the properties on the right bottom in internet explorer (yello sloth) to see what certificate is used it shows for all published SSL sites *.mydomain.nl in stead of owa.mydomain.nl or blabla.mydomain.nl at the common name / issued to:.

The second i cant figure out why it seas that there are non secure items in my owa site. All dirs are SSL like: public, exchweb, exchadmin, exchange. When i used the form based publish it never sead that.

(in reply to StarChase)

Post #: 3

RE: Wildcard cert issue's - 23.Sep.2004 7:19:00 PM

Jason Jones

Posts: 2265
Joined: 30.Jul.2002
From: United Kingdom
Status: offline

The browser will alwasy see *.domain.com as this is the cert that is bound to the ISA listener. If you are using SSL briding, it is ISA that is connecting to the back end server not the client.

Does is matter that all published sites shows as *.domain.com for the cert?

JJ

(in reply to StarChase)

Post #: 4