Click HERE to see how Saviynt Intelligence is transforming the industry. |
10/10/2024 06:42 AM
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
10/10/2024 06:47 AM
@sheldonz you can ask support team for a restart.. once
Also do validate the certificate.
10/10/2024 06:47 AM
10/10/2024 05:41 PM
@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.
10/10/2024 06:34 PM
Validate with IP and 389 port if its working
10/11/2024 06:53 AM
@rushikeshvartak on using IP and port 389 getting below error
10/11/2024 08:15 AM
It seems port opening issue. Please check your SSL certificate might be expired. Raise saviynt support ticket to restart all pods from backend