We use LDAP authentication in our applications and we also would like to set a session expire time. I tried to set an expire time in access group. Then I chose"Use PegaRULES Timeout" in auth service. When I tested, session expired as I expected and simple login screen appeared as in the attachment. But I couldn't login using my LDAP credentials. It says "information was not recognized". Is this normal ?
In PRPC 7.x there this problem were the password needs to be base64 encoded at the UI level because the engine is expecting it to be encoded when it gets. So the engine is trying to decode it before the timeout activity is called causing the Password parameter sent to the LDAP server to be wrong.
Thank you for your comment. I tried that local change but after I submitted the from with my credentials, the page has been routed to "url:port/PRWebLdap1/prweb" and the page error was displayed. However when I opened the "url:port/prweb", I was be able to continue my work. I think Pega verified my credentials.
But we are just using "url:port/prweb" for ldap authentication. After the form is submitted, it should route to "url:port/prweb". How can I configure this ?
Posted: 3 years ago
Posted: 8 Aug 2019 12:25 EDT
Chris Koyl (ChrisKoyl)
Senior Fellow, Technical Support, Runtime Engine
Value is /prweb/oujENJg8_ugf9gQ0u_JF0cJ2WVqDM5kL-c68FN8Z2lM%5B*/!STANDARD which is matching with the current url on the browser. But when the form is submitted url is changing to /PRWebLDAP1/prweb/oujENJg8_ugf9gQ0u_JF0cJ2WVqDM5kL-c68FN8Z2lM[*/!STANDARD?pyActivity=CheckServerConnection&Close=true&pzPostData=2115076906
Thus I get http 400 error. When I manually go to the only "/prweb" url, it redirects me to /prweb/oujENJg8_ugf9gQ0u_JF0cJ2WVqDM5kL-c68FN8Z2lM%5B*/!STANDARD and I continue my work as I logged in.