Last updated on MAY 30, 2017

Applies to:

Goal

Problem Explanation

Users opening two or more distinct Internet Explorer (versions 8 & 9) browsers should expect each to behave uniquely.  Distinct browsers should not interact for example:

• Applications or session activity in one browser should not interact with another browser.
• Opening a session in one environment (ex: PY), then opening second session in PD.  The PY session is disconnected.
• Opening a session then opening a second session.  If second session is refreshed, it will show the application from first session.
• Logging into one session with a UserID.  When opening a second session, user is automatically logged in without IE asking for new credentials.
• Opening any application from WebDev client and going to a form (Ex: Add form), then opening the same application again, the second launch opens to the Add form, not the original form.

 Microsoft Internet Explorer browser's session and cookie behavior have changed in the newer releases.

Symptoms

In a case where an end-user opens two independent IE browser sessions from a single Windows workstation, you will find that these two browsers will share the same session identifier and 'cookie'. This occurs despite the fact that the two browsers were invoked from a Windows Internet Explorer shortcut. A single 'cookie' shared between two browsers will yield unpredictable results. For instance, from the first browser one could open P00095 (Business Object Reservations) via Fastpath and click Find. From the second browser one could open P01012 (Work with Addresses) via Fastpath. From the second browser the end-user will see that two applications are now running - both P00095 and P01012. This occurs even though a single application was opened per browser. If one were to close the second browser the first browser will error upon first touch indicating the session had expired. This behavior occurs as a result of a shared 'cookie' used by two IE browsers.

Solution