Support Article
Issue with re-authentication JavaScript that loads on timeout
SA-2872
Summary
User portal is opened by accessing a development environment. The same portal is launched in their QA environment in another window -> Log in to the portal and log out. On returning to the development environment and trying to continue the work on a work object, a re-authentication pop up is shown. On entering the correct credentials, it shows that the work object is locked. On clicking ‘Release lock’ and opening the work object again, the CSS applied differs. There is a different background color to the work object.
Error Messages
NA
Steps to Reproduce
1. Log into one environment and open user portal.
2. Open a work object and start processing(do not complete).
3. Open another environment, login and then logout with the same credentials used in the first one.
4. Resume working on the work object opened in the 2nd step.
5. A re-authentication message pops up.
6. Complete the authentication and the font size and CSS of the work object changes.
Root Cause
Logging out of one environment was clearing out the session cookie for Internet Explorer process.
There is a HTML stream Web-Session-Return returned called during logging out from the EndSession activity.
That HTML stream has the following JavaScript code.
if(window.attachEvent){
document.execCommand("ClearAuthenticationCache","false");
}
This is clearing the session cookie and hence causing a re-authentication to happen and causing CSS issues.
Resolution
Removing the following JavaScript code from the HTML stream rule 'Web-Session-Return' resolves the behavior.
if(window.attachEvent){
document.execCommand("ClearAuthenticationCache","false");
}
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.