One Identity Safeguard for Privileged Sessions 7.1.1 - Administration Guide

Typo in SPP's address, the address is not reachable

• Error: The browser reports errors when SPS redirects to SPP's login page, for example, This site can’t be reached. The exact error message depends on the browser.

• Resolution: Click the Back button of the browser and enter the correct address into the SPP Address field.

Typo in SPP's address, the address is alive, but not an SPP

• Error: After clicking the Join button, a web site other than SPP's Login interface is displayed.

• Resolution: Click the Back button of the browser and enter the correct address into the SPP Address field.

SPP's HTTPS certificate does not match its IP address or hostnam

• Error message: Error joining to SPP: SPS has failed to join to SPP. For more information, see the error details. (JoinFailed)

• Raw error:

  {
    "response": "Error sending request: SSLError: HTTPSConnectionPool(host='examplespp.company', port=443): Max retries exceeded with url: /service/core/v3/Cluster/SessionModules (Caused by SSLError(CertificateError(\"hostname 'examplespp.company' doesn't match '192.0.2.123'\",),))",
    "status": null,
    "url": "https://examplespp.company/service/core/v3/Cluster/SessionModules"
  }

• Resolution:

  • If SPP's certificate contains SPP's IPv4 address in the Common Name or subjectAltName field, then enter that IP address when linking SPS to SPP.

  • If SPP's certificate contains only its DNS name in the Common Name or subjectAltName field, then use that hostname when linking SPS to SPP.

  • Otherwise, set up an SSL server certificate for SPP which matches its IP address in the certificate's Common Name or subjectAltNamefields (see SSL Certificates in the Safeguard Administration Guide) and retry linking. Wait about five minutes to let the timeout of the failed link request expire before starting a new link request after a failed incomplete one. (Alternatively, see Reversing the SPP to SPS join in the Safeguard Administration Guide.)

Typo in SPP credentials

• Error: Login to the SPP web interface fails.

• Raw error:

  {
          "error": "invalid_request",
          "error_description": "Access denied.",
          "success": false
      }

• Resolution: Make sure that the correct username and password are entered in the SPP username: and SPP password: prompts.

SPP user has insufficient permission

• Error message: Error joining to SPP: SPS has failed to join to SPP. For more information, see the error details. (JoinFailed)

   Authorization is required for this request.
  
         Code: 60108
         URL: https://192.0.2.123/service/core/v3/Cluster/SessionModules
         Status: 403

• Resolution: When SPS redirects to SPP's Login interface, then login as an SPP user has "Appliance" and "Operations" permissions.

SPS is already linked to SPP

• Error message: Error joining to SPP: SPS has failed to join to SPP. For more information, see the error details. (JoinFailed)

  The session connection has a missing, invalid, or non-unique
  value [ NodeId ].
  
         Code: 60657
         URL: https://192.0.2.123/service/core/v3/Cluster/SessionModules
         Status: 400

• Resolution: See Reversing the SPP to SPS join in the Safeguard Administration Guide.

Linking takes too long (more than five minutes)

• ERROR: Request to https://192.0.2.123/service/a2a/v2/PsmValidation failed, response (HTTP 403):

      {
          "Code": 60108,
          "Message": "Authorization is required for this request.",
          "InnerError": null
      }

• Resolution: Make sure that SPS is not overloaded and try linking again.