Share

Restrict Concurrent Sessions In Siebel

This thread is trageted to discuss the possible ways to restrict duplicate sessions in siebel application.

 

We have two scenerios.

  1. Duplicate sessions from single workstation
  2. Duplicate sessions from multiple workstations

 

 

 

Duplicate sessions from single workstation

 Duplicate session from single workstation can be restricted using IE8 feature of tabbed browsing.

  •   Tabbed browsing in IE8

Tabbed Browsing is not supported with Siebel beyond one active session per IE8 instance. Users can only run siebel in one tab. .User can open multiple web page in different tabs but only one live connection to a Siebel application

If we close an active Siebel session tab without logging out , next time the user open a new session it remains logged in.  This is a long-standing feature of Siebel. 

To completely disconnect from Siebel either use the "Logout" menu option in Siebel or close the IE8 browser instance.

 

 

 Duplicate sessions from mutiple workstation

 Not a very clean solution; write a script which periodically monitors for duplicate login sessions and then kills/terminates the newest sessions. It will not prevent users having duplicate sessions from multiple workstations, but will discourage them logging on twice (or sharing their account). 

Thanks to Pier Paolo Marzo and Peter van Nes for valuable inputs.

 Discussion is on. Please share your experience and implementation for restricting user for opening concurrent session in siebel.

9 comments on “Restrict Concurrent Sessions In Siebel”

  1. Ghous Fakhri Reply

    Dear Writer,
    The problem is not simple – especially, when sessions to be restricted are deliberate i.e., call center agent opening multiple instances of IE to meetup his/her KPAs or intentional attempts.
    Siebel opens a new connection for each separate window of IE. Please share some thoughtful practical approach about restricting the no of sessions in this particular scenario.
     
    Regards
    Ghous Fakhri

  2. Tejeshwer Reply

    One can put the logic in application load event and should log off the current session if there is an active tasks exist for the same user. 

  3. JhonnyB Reply

    Better try implementing Singleton concept for each Siebel user, how to achieve this you need to find out, why should a programmer share logic rather than sharing compiled code 🙂

  4. Obiora Reply

    If using Database Authentication, the number of session can be restricted using Database profile session limit. Once configured and assigned to the required users, any attenpt to open more than the number of sessions will give error

  5. Ashish Kr. Bameta Ashish Kr. Bameta Reply

    Obiora,

    Will this restrict duplicate sessions from a single user id?

  6. Seth Lytle Reply

    If you are interested in additionally auditing when and who logs in, you could write to a CX table a record of every user that is logged in at any given time. You could have columns for userID, login time, logout time and update them appropriately either through runtime event triggering a service or whatever. Check to see if the current user that is trying to log in has a record that doesn't have a logout timestamp and cancel their login by returning a cancelOperation on the ApplicationStart function… or maybe you can invoke a auto logout. I haven't tested any of this, but i'm sure you can get it to work (and also have an easy to monitor and report on user usage)

  7. Sandeep Reply

    On the contrary to this, if the user wants to have multiple active sessions, use New Session option of IE and login in that window again. This would let someone work across different active siebel sessions.

  8. Ashish Kr. Bameta Ashish Kr. Bameta Reply

    Sandeep, you mean single multiple sessions with single user id/credentials? User can open multiple session in different windows of pervious IE versions too.

  9. alberto Reply

    Like said Obiora, If you using Database Authentication, the number of session can be restricted using Database profile session limit. We have this method implemented our customer, we have two oracle profiles, one for normal user (only one session) and second for privileged user (f.e  sadmin, user administrators,…). I think that is posible for LDAP too

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!