No ratings
Saviynt Employee
Saviynt Employee

Use Case


The customer changed the URL in the ADSI connection from LDAP to LDAPS once the connection was moved to secure.

The connection failed with the below error-
2021-12-13/10:49:11.793 [{}] [https-jsse-nio-443-exec-1]  DEBUG adsi.SaviyntGroovyADSIService - Error : [headers:[Cache-Control: no-cache, Pragma: no-cache, Content-Type: application/json; charset=utf-8, Expires: -1, Server: Microsoft-IIS/10.0, X-AspNet-Version: 4.0.30319, X-Powered-By: ASP.NET, Date: Mon, 13 Dec 2021 10:49:11 GMT, Content-Length: 263], responseText:{
"status": "Failure",
"message": "Authentication failed.",
"messageCodes": "API_ERR_00004",
"errorDetails": "API_ERR_00004 : -2146233088 : Could not connect to connection string LDAPS:// : Unknown error (0x80005000)"
}, cookies:[], statusCode:400]
2021-12-13/10:49:11.802 [{}] [https-jsse-nio-443-exec-1]  DEBUG integration.ExternalConnectionCallService - EXIT invokeExternalMethod 




Applicable Version(s)



LDAPS format is not supported in the ADSI Connector.
You must always start the URL with LDAP for a secure or insecure connection.
Version history
Last update:
‎07/10/2023 11:00 AM
Updated by: