I'm not sure if I did right with the wildcard this time. Here what I did:
1. installed wildcard from Digicert 2. Exported to ISA server, I also installed the root and intermediate cert manually. 3. Created the web listener 4. Created stand alone cert 5. Removed wildcard from the web server and installed new cert from stand alone. 6. Installed the cert from stand alone to ISA (under trusted root folder) 7. Reboot web and isa.
My question: At Bridging Tab, I couldn't select "Use a certificate to authenticate to the SSL Web Server". I got error "There are no certificates configured on this server" I also tried to export the new cert from the web server to ISA (I don't think this is necessary) but I still couldn't select that option. Is this the way should be?
I'm not sure Tom, I thought we have to configure that. The published site (https) is working, I could access the site and when I ran ethereal on internal & external network, I can see that the packet between client-ISA-OWA Server is encrypted.
Another question: I did that setup on temp server, on my ISA I will published: OWA(SSL, Nfuse(SSL), E-Sales (http), we'll change to SSL as soon as we finish upgrading the web. What will happen with E-Sales site if I choose only basic auth on ISA? Is the username and password sent with clear text? How about if I choose basic and integrated?