Why can't SSL be easier???

  • Thread starter Thread starter Paul King
  • Start date Start date
P

Paul King

All I want to do is setup Certificate Authority on my Win2k server and issue
a Certificate for the same server running OWA.

The server itself is hidden behind a firewall using NAT - but I always get a
dialogue box when external users access HTTPS OWA. If I try and install
this certificate into my Trusted Root Certification Authorities - this won't
allow me.

All I want is a easy document that tell me what to do - please help.

Regards
Paul
 
I think this happens when the certificate is not created under the same
public name you're using to access OWA (pardon my vagueness), but I've
played with this a lot and always get prompted no matter how I set it up.

You could go with Verisign or something like that, but what's the real
problem with users having to click to accept a certificate?
 
Only that its inconvenient I guess.

It would be nice if the import worked without a hitch so that the
certificate is issued only to clients wanting access to the OWA server.

Cheers
Paul.

"Lanwench [MVP - Exchange]"
 
You can buy a Verisign certificate or something like that if you like...me,
I'm cheap, so I just click Accept. :-)

Paul said:
Only that its inconvenient I guess.

It would be nice if the import worked without a hitch so that the
certificate is issued only to clients wanting access to the OWA
server.

Cheers
Paul.

"Lanwench [MVP - Exchange]"
I think this happens when the certificate is not created under the
same public name you're using to access OWA (pardon my vagueness),
but I've played with this a lot and always get prompted no matter
how I set it up.

You could go with Verisign or something like that, but what's the
real problem with users having to click to accept a certificate?
Click to expand...
Click to expand...
 
I think I have solved this - the certificate *.cer file can be imported to
each client if they have the *.cert file itself.

Thanks matey
Paul.

"Lanwench [MVP - Exchange]"
You can buy a Verisign certificate or something like that if you like...me,
I'm cheap, so I just click Accept. :-)

Paul said:
Only that its inconvenient I guess.

It would be nice if the import worked without a hitch so that the
certificate is issued only to clients wanting access to the OWA
server.

Cheers
Paul.

"Lanwench [MVP - Exchange]"
I think this happens when the certificate is not created under the
same public name you're using to access OWA (pardon my vagueness),
but I've played with this a lot and always get prompted no matter
how I set it up.

You could go with Verisign or something like that, but what's the
real problem with users having to click to accept a certificate?

Paul King wrote:
All I want to do is setup Certificate Authority on my Win2k server
and issue a Certificate for the same server running OWA.

The server itself is hidden behind a firewall using NAT - but I
always get a dialogue box when external users access HTTPS OWA. If
I try and install this certificate into my Trusted Root
Certification Authorities - this won't allow me.

All I want is a easy document that tell me what to do - please help.

Regards
Paul
Click to expand...
Click to expand...
Click to expand...
 
Back
Top