Exchange2010 and SSL

No knowledge of the PKI system and have a question hope experts will shed the light on this.
Have CAS server configured and isnatlled third party trusted SAN certificate on the CAs server because os OWA.
The OWA is ssl setting configured to ignore the client site certificate.
We have internal CA is running and issuing users certificate to all AD users via auto enrollment policy. The internal CA has its self signed certificate so it is issuing the certificate as the root CA for the org.
Will the users able to connect OWA  if i enabled the OWA setting to client certificate to require?
or Do the users require certificate from third party where i got it for CAS server?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
You are mixing up the certificate types.
The internal CA you are using is for authentication.
The SSL certificate on the OWA virtual directory is for the connection.

If you choose to require client certificates then you will cause OWA to almost certainly stop working correctly, particularly for users connection from the outside world.

Leave it as it is, with the trusted SSL certificate on the web services directory and have users authenticate with a username and password.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Will SzymkowskiSenior Solution ArchitectCommented:
For Simplicity I would recommend keeping your internal and external URL for Exchange the same. This way you only need to worry about one fqdn and no longer need to remember server names for internal URL's etc.

You will need to setup a split-brain DNS creating a internal zone for your External FQDN on your DNS servers. From there you create your A records for and then users internally will use the same FQDN as external.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.