My Oracle Support Banner

Error: 'The User Has Already Reached The Maximum Allowed Number Of Sessions' After Clicking Disconnect To Logout P6 Professional Configured For Client Side Cache Using SSO (Doc ID 2478824.1)

Last updated on MARCH 01, 2019

Applies to:

Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 18.7 and later
Primavera P6 Enterprise Project Portfolio Management - Version 18.8 to 18.8.3.0 [Release 18.8]
Information in this document applies to any platform.

Symptoms

When attempting to click the disconnect button from the P6 Professional login page (after already having connected using Cloud Connect (client side cache enabled) with Single Sign On (SSO) setup for Cloud Connect), clicking disconnect launches a secondary window (this occurs because a "logout URL" is defined under the configuration in use for Cloud Connect) but loads a SAML Identify Provider (IdP) "signing in" window for a couple seconds then results in an Oracle Service Provider (SP) page to display with the following error:

ERROR
--------
The user has already reached the maximum allowed number of sessions. please close one of the sessions before trying to login again


Note: This error is indicative of multiple sessions being created under the Oracle SP until reaching the "Maximum number of sessions per user" threshold (by default, 8).


STEPS
--------
The issue can be reproduced at will with the following steps:

  1. Configure an SSO Logout URL under the P6 Professional Cloud Connect Configuration:
    1. Launch the Administration Application for P6
    2. Browse to $configuration > application
    3. Set a logout URL
    4. Save changes and restart Cloud Connect
  2. Launch P6 Professional login page
  3. Click an alias configured for:
    • SSO
    • Client side cache
  4. Click Connect
  5. At the SSO window which launches, authenticate (if using a form based authentication)
    • Note, P6 Professional login begins.
  6. Once P6 Professional is loaded, click File > Exit.
  7. Click Yes to confirm exit of P6 Professional
    • Note, the cache service (Primavera.CacheService.exe) should remain running in background.
  8. Launch the P6 Professional login page
    • Note, the cache service should indicate on page that it is already connected.
  9. Click Disconnect


BUSINESS IMPACT
--------
This causes the user to be locked out of P6 Professional until the user's inactive sessions generated under the SP to terminate after exceeding the "Idle Timeout" threshold.


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.