Does a certificate error in OWA due to a name mismatch bypass the security of the certificate?

We use RPC over HTTP and use an SSL certificate for that.  The certificate is assigned to a FQDN  Some of our users access OWA using instead of the FQDN.  They of course get the certificate error The security certificate presented by this website was issued for a different website's address.  

My question is if they click continue and access OWA anyway, does that bypass the certificate and its security?  Or does the certificate still work correctly for that connection?
Who is Participating?
tigermattConnect With a Mentor Commented:

The site will still be secure, the user's must simply click past an annoying warning message to login. The only purpose of the SSL warning screens when there is a name mismatch is to warn users that their supposedly 'secure' connection has not had its certificated generated by a secure, trustworthy authority.

The security feature is mainly intended at public sites; when employees are involved I just tell them it's not a problem for logging in to their webmail and just to click past it.

Andres PeralesConnect With a Mentor Commented:
still works other words the link between client and server is still secure...
AiBrianAuthor Commented:
Thanks for the quick response and clear response.  
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.

All Courses

From novice to tech pro — start learning today.