E-LDAP: Why Does LDAP Authentication Signon PeopleCode Execute for PeopleSoft Authenticated OPRIDs?
(Doc ID 1453692.1)
Last updated on APRIL 25, 2019
Applies to:PeopleSoft Enterprise PRTL Interaction Hub - Version 9.1 and later
Information in this document applies to any platform.
Customers are noticing after upgrading to PT 8.5x that the Signon PeopleCode for LDAP Authentication is getting executed even for already authenticated PeopleSoft logon users like PS and GUEST. This should not be happening because the SetAtuhResult value during logon is equal to TRUE and therefore it should skip the LDAP_AUTHNETICATION signon PeopleCode and exit. But this is not happening so PeopleSoft authenticated users are receiving a lot of unnecessary GETCERTIFICATE calls logged in the app server log. For the GUEST account this is using up all app server processes and not allowing anyone to logon.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document