If you enable the unified messaging service on Unity Connection you have the option to validate the SSL certificates. For some reason it's not working. I really don't have solid expertise in Exchange or with server certificates, so I'm reaching out for some help. Environment: Exchange 2013 64-bit on Windows server 2008 R2 64-bit.
To me it's not clear what is going wrong, if it's exchange or unity connection that throws the error. I find the Cisco documentation not clear on this subject. It doesn't state what specific certificates need to be uploaded on CUC, so I took the root certificate and the server certificate. I uploaded both to 'tomcat-trust' and 'connection-trust' as descibed in the docs. In Wireshark traces I can see an encrypted handshake and no errors.
As this is a lab environment I don't have signed certificates, so I converted them with openssl (.der to .pem). In the troubleshooting guide they provide the workarround by not enabling this certificates validation. Is it even supposed to work like this?
I tried to change some settings from what I found in several other posts on this forum, but the problem remains.
Is there another way to test this?
What traces can be looked at on CUC to see what's going wrong with the certificates?
Thanks for the answer. I guess I must have been too tired that night to read complete documentation (or just too lazy). The documentation is indeed clear on this:
"Self-signed certificates cannot be validated. If you selected HTTPS from the Web-Based Protocol list, and if you are using self-signed certificates, do not check the Validate Certificates for Exchange Servers check box. If you do check the check box, Connection will not be able to access Exchange"
Now that's an easy 5 points (for the effort on answering n00b questions).
But why not changing the parameter to "Validate public certificates for Exchange Servers" if that's the only way to go? Must just been me...
Well, I don't have much say in whether or not the parameter name itself should be changed. I don't really see it as being an issue but that's my opinion. In general, I don't typically use certificate validation but, like everything, I'm sure there are 2 sides to that story depending on who you talk to.