• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Signing Users Out When They Close the Browser

mattbbpl

Member
We are running JD Edwards EnterpriseOne 9.1, and we have SSO/WNA successfully enabled using Oracle Access Manager. This all works great. When users launch JDE initially it will automatically log them in using their desktop credentials, and if they launch another tab and navigate to JDE the new instance will use the same pre-existing session. We allow for a handful of sessions to be created because, inevitably, some users will close the browser without signing out or a computer crashes while a session is in use or... something.

However, a new workflow caused us an issue today that I'm unsure how to handle. Users receive JDE notifications (in email) to approve a Purchase Order Requisition. This launched the Approval Order Requisition Approval window with no JDE menu items of any kind (including the sign out option). When the user clicks the "Approve" option on the screen, the window closes without going through the sign out process.

If a user has another tab open (even if it's just to something like Google), then each time they click one of these links it will open a new tab in the same browser instance, reuse the session created from the first time they clicked one of these links, and everything is fine.

However, if they have no browser tab open initially, then every time they open and approve one of these links it will create a new session on the SSO provider (Oracle Access Manager) and leave it orphaned once the browser closes.

A user attempted to do this 53 times in a row the other day.

Is there a way to force JDE to go through the Sign Out mechanism when a browser is closed? Ideally this would occur when the browser instance is closed in it's entirety rather than just the current tab, but I'll take insight into any available options at this point.

Thanks in advance,
Matt
 

Larry_Jones

Legendary Poster
"A user attempted to do this 53 times in a row the other day." - Give that user a Gold Star! Ya gotta admire persistence.

Seriously though Matt if you find a way to make the browser close automatically execute logoff please share it with the group. As far as I know there is no published method.

Cheers
 

mattbbpl

Member
"A user attempted to do this 53 times in a row the other day." - Give that user a Gold Star! Ya gotta admire persistence.

Seriously though Matt if you find a way to make the browser close automatically execute logoff please share it with the group. As far as I know there is no published method.

Cheers
That's unfortunate. Thanks for your reply, though. It's good to have confirmation.

There are procedural workarounds such as leaving an additional tab open (even to something basic like Google's main page) so that the session isn't lost on the client when the screen is closed, but users see those as hacks (and they're not really wrong).
 

ice_cube210

VIP Member
Does the LogoutOnBrowserClose setting in the JAS.INI not do what you expect it to do ?

I have not tested in the multiple tab / OAM workflow link scenario , but it works fine other wise.
 

mattbbpl

Member
Does the LogoutOnBrowserClose setting in the JAS.INI not do what you expect it to do ?

I have not tested in the multiple tab / OAM workflow link scenario , but it works fine other wise.
For whatever reason, this is not ending the session in OAM. The OAM session remains orphaned.
 
Top