Login issues with Pega Labs for an LDAP user
Hi Team,
We are facing login issues with Pega Labs for an LDAP user. (We are able to connect as administrator).
Could you please help us to solve this issue. Thank you!
***Edited by Moderator Marissa to update Platform Capability tags****
Pegasystems Inc.
IN
You can go through below article for unlocking the account and to reset the passwords in an automatic way
https://community.pega.com/knowledgebase/articles/configuring-login-security-and-password-policies
Pegasystems Inc.
IN
Thanks for your reply!
Yes, there is an issue while logging in to the LDAP url of my internal application that I have developed for my team.
It was working fine for many months, but all of a sudden, the users were unable to login.
Am not a developer as such, so I am not sure if there should be any changes to be made within the dev environment. Your help would me much appreciated.
Thank you!
Pegasystems Inc.
IN
Thank you for your help on this!
I am unable to get the log files.. However, I have go the same error again and I hope it's covered in this log.. So, I am attaching the latest log now. Hope it helps to solve the issue!
Attached is the log file!
Pegasystems Inc.
IN
Hi ,
when you the check the below exception in the log, Ldap server is not reachable. getting timedout exception.
please do test connectivity on "records -> sysadmin -> Authentication service -> open the ldap service rule -> do test connectivity for jndi binding "
if test connectivity failed then reach out to the respective team to make sever up.
Hi ,
when you the check the below exception in the log, Ldap server is not reachable. getting timedout exception.
please do test connectivity on "records -> sysadmin -> Authentication service -> open the ldap service rule -> do test connectivity for jndi binding "
if test connectivity failed then reach out to the respective team to make sever up.
"External authentication failed: javax.naming.CommunicationException: <host & port of ladp server> at com.sun.jndi.ldap.Connection.<init>(Connection.java:236) ~[?:1.8.0_242] at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:137) ~[?:1.8.0_242] at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1609) ~[?:1.8.0_242] at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) ~[?:1.8.0_242] at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) ~[?:1.8.0_242] at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) ~[?:1.8.0_242] at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) ~[?:1.8.0_242] at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) ~[?:1.8.0_242] at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) ~[?:1.8.0_242] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) ~[?:1.8.0_242] Caused by: java.net.ConnectException: Connection timed out (Connection timed out) at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_242] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_242] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_242] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_242] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_242] at java.net.Socket.connect(Socket.java:607) ~[?:1.8.0_242] at java.net.Socket.connect(Socket.java:556) ~[?:1.8.0_242] at java.net.Socket.<init>(Socket.java:452) ~[?:1.8.0_242] at java.net.Socket.<init>(Socket.java:229) ~[?:1.8.0_242] at com.sun.jndi.ldap.Connection.createSocket(Connection.java:373) ~[?:1.8.0_242] at com.sun.jndi.ldap.Connection.<init>(Connection.java:213) ~[?:1.8.0_242] "
Pegasystems Inc.
IN
Hi,
I have reached out to Pega Labs and they say -
The server with which connectivity is getting tested, that is Proprietary information hidden is down. Can you check ldap server’s ip ?
Also, Attached is the latest Log file.
Could you please check and let me know.
Your help is much appreciated. Thank you!
Pegasystems Inc.
IN
Hi UdaySree,
" Proprietary information hidden:389" this is ldap server ip & port which is not reachable from the server where prweb deployed.
let us know still you have any queries