- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2014 04:55 AM
Hello,
When I click the "Test Connection" Link in LDAP Server,I am getting the following error :
LDAP:Simple Bind Failed
LDAP:Communication Error:Simple Bind Failed
LDAP:javax.net.ssl.SSLException:java.langRuntimeException:Unexpected Error:java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty.
Connection Environment Used :
How to overcome this issue?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2014 03:30 PM
We are having the same issue. We had it once before and had to reload the certificate into the SAML2 Keystore. This time, however, the problem is not resolved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2014 06:30 AM
Hi,
First, did you try connecting to your LDAP server using your credentials and an alternate software for validating all parameters ? (LDAP browser)
Then your issue seams to be related to LDAPS... did you chek the ssl box and uploaded the certificate in Snow ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2014 07:51 AM
Hello ,
It was working fine earlier ;
May be a day or two ,its throwing this error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2014 08:03 AM
This error message could have many explanations :
- Your certificate has expired / no more valid => upload generate a new Certificate
- Your certificate Key Store is invalide => valid your keystore with : http://wiki.servicenow.com/index.php?title=Uploading_an_LDAP_Certificate#Validating_Certificates_and...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2014 03:30 PM
We are having the same issue. We had it once before and had to reload the certificate into the SAML2 Keystore. This time, however, the problem is not resolved.