Re: SSL connecting on OWA 2003
- From: "Nathan B [MSFT]" <nbigman@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Apr 2006 13:25:18 +0300
You need a certificate for any connection that is over HTTPS. You already
have one for the connection from ISA Server to the OWA server. Since your
clients will connect to ISA Server over HTTPS, you need another certificate
on ISA Server. The name on the certificate will have to match the name that
the user uses to connect to the site (the published, public name). Also,
each client computer will require the root certificate for that certificate.
If you can meet those conditions, you could theoretically use the same
certificate as the one on the OWA server, but it doesn't seem too likely.
See the document "Digital Certificates for ISA Server 2004"
(http://www.microsoft.com/technet/prodtechnol/isa/2004/plan/digitalcertificates.mspx).
Most of the information will be relevant for ISA Server 2000.
--
Nathan Bigman
ISA Server Product Team
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"2Tian" <cmchong20@xxxxxxxxx> wrote in message
news:O%239gNQbUGHA.2156@xxxxxxxxxxxxxxxxxxxxxxx
Windows server 2003, Exchange 2003, ISA 2000.
I have created a Windows own Certificate in front-end (OWA server).
Internal client users have no problem access OWA via https , but not
external client users. I was told that i have to configure certificate for
ISA 2000 server as well.Can i use the same certificate in front-end or
create a Windows own CA ? What should i do ?
Below is the draft diagram of my network config:
internet-->FW-->DMZ-->ISA2000-->DMZ--->FW--->FE(CA)domain
member--->BE(domain member)
.
- Prev by Date: Need help with publishing....
- Next by Date: Re: Need help with publishing....
- Previous by thread: Need help with publishing....
- Next by thread: Re: Published Web site reporting software???
- Index(es):
Relevant Pages
|
