User Single Sign On

The Single Sign-On (SSO) architecture allows the user to sign on to your application and subsequently authenticates the user with the Management Portal. 

The user does not need to enter separate login credentials.  The session ID established during the authentication is valid until the current session is terminated when the user logs out or your application times out.

The sequence is as follows:

  1. The user is initially authenticated in your application after entering their login credentials.  The credentials are then mapped with the API session ID and the org ID to validate if the user can access the Management Portal. 

  2. When the user requests access to the Management Portal, an encrypted session ID with the public key generated by the organization administration are passed as a token to open the Management Portal.

  3. After validation, the user has access to the Management Portal.