Skip to end of metadata
Go to start of metadata

This example explains a whole SSO process on the intranet of an imaginary COMPANY with an imaginary USER.

Process overview

  1. USER signs in to the COMPANY intranet
  2. USER tries to visit Verba web interface
  3. COMPANY intranet generates an SSO Registration request with a Security Token
  4. COMPANY intranet sends the request to Verba Media Repository
  5. Verba Media Repository verifies the request, registers Security Token and responds
  6. COMPANY intranet uses the Security Token to provide the USER with an SSO Login URL
  7. The user is logged in without repeated authentication

The same process described with more details

  1. USER signs in to the COMPANY intranet with their regular process (e.g. password, Windows authentication, biometrics, etc.)
  2. In the COMPANY intranet USER clicks on a link or tab that leads USER to the Verba web interface
  3. COMPANY intranet generates an SSO RegistrationHTTP request with required parameters:
    1. Verba Environment ID (applicable only to multi-tenant Verba systems)
    2. Verba User Name
    3. Globally Unique Security Token (GUID)
    4. Requested Expiration Date of the Security Token
    5. Current IP address of the USER
  4. COMPANY intranet sends the HTTP request to the Verba Media Repository
  5. Verba Media Repository verifies that the HTTP request comes from the COMPANY intranet based on IP address and registers the Security Token with expiration date and USER IP address, and replies to the COMPANY intranet with a status
  6. On successful status response the COMPANY intranet uses the Security Token to provide the USER with an SSO Login URL that allows login to the Verba web interface without further authentication
  7. The user is logged in without repeated authentication
  • No labels