If you are using the ePortal Web or Mobile interfaces, you can notice that two or more instances of a browser do not create separate sessions to the host application automatically. This is because; by default IIS uses machine level cookies for session management. Hence, multiple browser instances re-use the same cookies and cause confusion if all the browser instances are connecting to the same application.

To avoid this problem, set the cookieless property in the Web.config file to true. To do this - in the <system.web> section in Web.config file, add <sessionState cookieless="true"></sessionState>.

This ensures to propagate the session state as part of the browser URL when accessing the application, and independent sessions are created for multiple instances of the browser.

You might notice that this configuration is not required for previous versions of the Internet Explorer. However, from Internet Explorer 11 (IE 11) onwards, a new browser instance on the same machine shares the same session. So, for using multiple browser sessions for the same application on one machine, create an independent IE session from File > New Session. This allows you to create a new session of the same application for different IE instances.