Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

AD Connection Failing in DEV

sheldonz
New Contributor
New Contributor

Hello,

Our new AD connection from Dev is failing, we have imported the SSL certificate, performed the restart. Saviynt team also confirmed the DNS resolver is resolving to the required hostname

2024-10-10T09:20:04-04:00-ecm-ldap.SaviyntGroovyLdapService-http-nio-8080-exec-3-jk8wh-DEBUG-server, managedn LDAPS://onxxxxxxxx.xx:636CN=svc_dev_saviynt,OU=ServiceAccounts_SAVIYNT,OU=SAVIYNT_DEV,OU=xxxx,DC=xx,DC=oxxxx,DC=xx
2024-10-10T09:20:04-04:00-ecm-ldap.SaviyntGroovyLdapService-http-nio-8080-exec-3-jk8wh-DEBUG-Checking for url = LDAPS://onxxxxx.xx:636
2024-10-10T09:20:04-04:00-ecm-ldap.SaviyntGroovyLdapService-http-nio-8080-exec-3-jk8wh-ERROR-Exception in verifyDN :::
2024-10-10T09:20:04-04:00-ecm--null-jk8wh--javax.naming.CommunicationException: onxxxxxxxx:636 [Root exception is javax.net.ssl.SSLException: Connection reset] at com.sun.jndi.ldap.Connection.<init>(Connection.java:243) at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:137) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2849) at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:347) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxFromUrl(LdapCtxFactory.java:229) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:189) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:247) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:695) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) at javax.naming.InitialContext.init(InitialContext.java:244) at javax.naming.ldap.InitialLdapCo

6 REPLIES 6

NM
Honored Contributor III
Honored Contributor III

@sheldonz you can ask support team for a restart.. once 

Also do validate the certificate.

rushikeshvartak
All-Star
All-Star
  • Restart server

Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

shreyascn18
New Contributor II
New Contributor II

@rushikeshvartak  do you mean Application restart from the Saviynt UI? If yes, then the UI restart is already done but still have the same issue. 

Validate with IP and 389 port if its working


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

shreyascn18
New Contributor II
New Contributor II

@rushikeshvartak  on using IP and port 389 getting below error

2024-10-11T09:50:10-04:00-ecm-ldap.SaviyntGroovyLdapService-http-nio-8080-exec-8-jk8wh-ERROR-Exception in verifyDN :::
 
2024-10-11T09:50:10-04:00-ecm--null-jk8wh--javax.naming.AuthenticationNotSupportedException: [LDAP: error code 8 - 00002028: LdapErr: DSID-0C09032F, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v4563] at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3252) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3207) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2993) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2907) at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:347) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxFromUrl(LdapCtxFactory.java:229) at com.sun.jndi.ldap.LdapCtxFactory.getU

It seems port opening issue. Please check your SSL certificate might be expired. Raise saviynt support ticket to restart all pods from backend


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.