From Bright Pattern Documentation
Jump to: navigation, search
• 5.19 • 5.3 • 5.8


Sessions

A session is defined as a “authenticated state” of the user and is uniquely identified by a session token (cookie). It is separate from the “logged in” state for an agent. An agent can login and logout several times by closing and reopening the browser tab with the Agent Desktop application and remain within one authentication session.

Multiple sessions for the same user are enforced by each application server separately for each application type:

  • For Agent Desktop, only one logged in state (and therefore, one session) is allowed. Otherwise, two browsers with two valid sessions will fight for one agent login.
  • For wallboards, only one session is allowed. Otherwise, it is hard to find out who is using up all concurrent logins per tenant and extra sessions would be creating unnecessary server load.
  • For Contact Center Administrator, more than one session is allowed.
    < Previous