E1: JAS: JSESSIONID Cookie Left Behind After Signoff on Local Web Client Affecting Subsequent Sign-ins (Doc ID 1918836.1)

Last updated on MAY 20, 2019

Applies to:

Symptoms

You have noticed the below behavior when working on Local Web Client:

Scenario 1:

1. On a JDE Web Development Client, start a WEB session by clicking the "EnterpriseOne Menu" under Tools Menu - the very first time, a properly signed-in JDE WEB session will appear.
2. Sign Off in this session, leaving the browser open or if there are any other IE browser windows open, this JDE window can even be closed.
3. Attempt to start a new WEB session by clicking the "EnterpriseOne Menu" under Tools Menu - the window will open with a login prompt, i.e.: the signon did not happen.

Expected Results - When attempting to launch the Web Part second time, system should not prompt for the login credentials and take you in directly based on the existing cookies.

Scenario 2:

1. On a JDE Web Development Client, start a WEB session by clicking the "EnterpriseOne Menu" under Tools Menu - the very first time, a properly signed-in JDE WEB session will appear.
2. Sign Off in this session and close all the browser sessions as well.
3. Attempt to launch the Web Part by clicking the "EnterpriseOne Menu" Tools Menu - you will be automatically logged in.

Expected Results - When attempting to launch the Web Part second time, system should prompt for login credentials instead of taking users directly in, because Sign-off and closing all the browser session should clear the existing cookies.

Cause

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