Support articles
Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.
SSL server certificate could not be verified when logging to the Policy Manager Console using Active directory LDAPS in
Last updated
Issue:
I am not able to authenticate to Active Directory using LDAP or LDAPS, it give me a SSL certificate could not be verified error.
Resolution:
Troubleshooting steps:
- Check if port is not specified, Policy Manager uses 389 for plain LDAP and 636 for LDAPS.
Note: Policy Manager does not have any fallback logic, it connects via protocol, address and port specified during user/group import.
- To trust this CA it should be imported to trusted root CA at the host (at Windows) or java keystore (at both Win and Linux), otherwise Policy Manager won't trust the server certificate, like openSSL does.
- You have to import CA cert that issues certs for LDAPS to Policy Manager host like instructed here
- You need to replace LDAPS cert with some properly issued by globally trusted CA in the chain
Note: The most common cause of a "certificate not trusted" error is that the certificate installation was not properly completed on the server (or servers) hosting the site. After you have imported the certificate, make sure its valid and install it on the Policy Manager Host