Last updated on AUGUST 02, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
SSO via OAM does not have a graceful shutdown on window close without logoff.
This behavior is different to the normal web without OAM enabled, user closes browser does shut down gracefully.
If a user is in JDE using Single Signon via the OAM application, if the browser is closed (without signing out E1), the sessions remains behind in both OAM and JDE. The sessions become orphan and eventually time out, but for JDE this is an hour and OAM is 8 hours, so these are using resources. If the same user does this eight times (Login E1 and close browser without signing out), on the ninth attempt, it will reach the session maximum for OAM and get an error message.
Sessions should be ended when browser is closed even if OAM is enabled.
The issue can be reproduced at will with the following steps:
1. Login JDE via OAM
2. Close browser
3. Check OAM session, session will be available for 8 hours after browser is closed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms