PeopleSoft Recruiting Candidate Gateway Session Restarted On The Default Site After Public User HTTP Session Inactivity Timeout Closes The Session (Doc ID 2485122.1)

Last updated on DECEMBER 20, 2024

Applies to:

Symptoms

Original Description:

The External Candidate Gateway is connected using a PT Web Profile which has the Public User ENABLED.
When the Public User session closes, based on the configuration of the Public User HTTP Session Inactivity parameter, at the next click Weblogic starts a new session for the Public User.
The new session uses the MENU.COMPONENT and goes to the Global Search page.  For Candidate Gateway, this is the Careers page.
Weblogic does not know about the CG SiteID used in the original session and goes to the Default SiteID.

If the applicant's original session accessed other than the Default SiteID, then the Search Results will not match. 
Confusion and errors could result, depending on the Recruitment Sources used to Post Job Openings and how those are assigned to SiteIDs.

STEPS

1. Applicant accesses the External Candidate Gateway using two Sites for two different companies.
2. When any site times out, the site no longer works correctly.
3. It takes you to the Main Entry page, and the Applicant search on Jobs again results in ALL jobs (not site specific jobs) being shown
The applicant may see the following type of error:
User receives error message "Job Opening XXX is no longer available. We are sorry the job(s) you have selected is no longer available. Please select another one."
User has to re-navigate to the entry url, or close browser and navigate back.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.