Re: SSL Certificate on OWA server
From: Steve Carr (scarr_at_bastyr.edu.NOSPAM)
Date: 11/04/04
- Next message: Nick Clark: "Re: OWA Internal/External Issue"
- Previous message: Lee Derbyshire [MVP]: "Re: OWA Internal/External Issue"
- In reply to: Ivan92: "SSL Certificate on OWA server"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 4 Nov 2004 12:30:56 -0800
you can use a stand alone CA just fine if you'd like. Just treat the IIS
process as if you were going to send it off to Verisign. Take that cert text
file and go to your CA and process it and then take the resulting cert file
back to the IIS process. If you want to make the cert warning go away for
users you can publish the CA's cert so that people can add it to their
trusted root CA's in IE, etc and then all will be well.
"Ivan92" <Ivan92@discussions.microsoft.com> wrote in message
news:421E30FE-FDC7-4480-AC28-F30B9D95842D@microsoft.com...
> What is the best method to add a free certificate to the OWA server
(rather
> than making Verisign et all richer)?
> I built a standalone machine as a certification authority and created a
> certificate which is working ok (it works, but the annoying " ... was
issued
> by a company you have not chosen to trust ..." takes a few seconds to come
up
> and then the user has to click on Yes). - Article 297681 addresses this
> issue, but the question is:
> Should the certification authority be linked to AD or is it better to have
a
> standalone?
>
> I haven't had much luck with AD, as if I match the machine name, I can
issue
> the certificate no problem but then the certificate does not match the
alias
> name. If I try to issue it to the alias (email.company.com) then cert
auth
> in AD complains that it doesn't match any template - any suggestions on
this?
>
- Next message: Nick Clark: "Re: OWA Internal/External Issue"
- Previous message: Lee Derbyshire [MVP]: "Re: OWA Internal/External Issue"
- In reply to: Ivan92: "SSL Certificate on OWA server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|