Introduction: The PeopleSoft ERP Agent be configured to allow actual usernames using 'psadmin' tool, rather than 'DEFAULTUSER' for all connections. Instructions: The short of this is that it is the PSAdmin tool of Peoplesoft is not updating.
PeopleSoft Enterprise PT PeopleTools - Version 8.54 to 8.54 [Release 8.4] Information in this document applies to any platform. ***Checked for relevance on Nov 3 2017***. There have been several PeopleSoft Timeout problems that have impacted various levels of 8.50, 8.51, and 8.52. Indications are all these problems are fixed now. There are also the old trusty values kicked out from Tuxedo with psr, pq, pclt, and the less commonly used psc.
For a better understanding of the SiteMinder process, here are the details of how we connect:. After the End user has been authenticated and authorized through the SiteMinder Policy Server, Policy Server returns the PeopleSoft UserID (PSUSERNAME user attribute response) to the Web Agent, which sets it as an HTTP request header. The Web Server (which is acting as a reverse proxy server), then forwards the request to the PeopleSoft Web Server along with the Siteminder session header.
PeopleSoft Servlets running on the PeopleSoft Web Server uses the DEFAULTUSER credentials to connect to the PeopleSoft Application server running Tuxedo via Jolt and transmits the HTTP request to the Application Server. PeopleSoft Application Server verifies the connection information and if successful invokes the SignOn PeopleCode. The SignOn PeopleCode retrieves the existing Siteminder session information from the HTTP headers and calls the SMPSLoginLib library to validate the session information which in turn verifies it from the Policy Server. SMPSLoginLib returns the result to SignOn PeopleCode and the SignOn PeopleCode passes on the PeopleSoft UserID (contained in PSUSERNAME header) to the PeopleSoft Application server for setting the PeopleSoft security context of that user and creating the PeopleSoft session. To summarize, the DEFAULTUSER has a role only in establishing the initial connection between the Java Servlet Engine of the Application server. The user session is created using the UserID that has been authenticated and authorization by Siteminder Policy Server.
The DEFAULTUSER account has no access to the system with or without SiteMinder's approval; if someone were to obtain and attempt to use that account without SiteMinder, no access would be granted and no data would be available. How can the ERP Agent/PeopleSoft be configured such that the actual username is displayed in 'psadmin', rather than the 'DEFAULTUSER' account?
After the Jolt timeout period, the actual username is shown instead. This would seem to indicate it may be possible to properly configure this to allow for the actual username to appear. ERP Agent plays no role in updating the Client Status to be shown by the psadmin utility and there is no configuration that can be done on the ERP Agent side to update the statistics shown by the psadmin for Client status.
The behavior that psadmin exhibits after Jolt timeout is specific to the tool itself and ERP-Agent side configuration does not has any role to play in it. For details regarding how psadmin utility lists down the Client Status and on what parameters these values are updated, the way forward would be to get in touch with PeopleSoft support.