1. Security Guide
  2. About Siebel Session Warning Message

About Siebel Session Warning Message

If multiple tab browsing is not configured for your application and you try to start a second Siebel session while another session is currently active, then a Siebel session warning message similar to the following appears. For more information about configuring multiple tab browsing, see Configuring Siebel Open UI.

You have initiated a Siebel Session while another Siebel session is currently active.  
Please choose the option that applies to you:
- You already have a Sieble session with unsaved data running in another window. To save 
  data from a second session go to the already open session and either save and exit 
  or continue to use that data.
- You do no have unsaved data in your other session and wish to close it and launch a new
  session. Click here.
- You have closed your previous Siebel browser instance using the Close button instead of 
  the Logoff feature and wish to open a new Siebel session. Click here.

After a successful UI login to Siebel application, two cookies are sent as follows:

  • Siebel Session Number. This cookie is the security token passed along with the request. It is encoded and holds valuable information required to connect to the correct task. Siebel Session Number remains until you explicitly log out of the application or close your browser.

  • [sameuisession]. This unique cookie is attached to the particular browser tab from where a user request is sent. It is set in javascript and expires after 3 seconds when the application unloads like it does when you close the browser (for releases prior to Siebel CRM 17.x, [sameuisession] expires after a year).

This effectively means the following:

  • If you close the (first) tab, the [sameuisession] will expire after 3 seconds and if you try to use the same Siebel Session Number from another (second) tab, then the Siebel session warning message appears.

  • If you try to run the application URL from another tab, the Siebel Session Number will be sent correctly but since no [sameuisession] is set, the Siebel session warning message appears.