This document describes the Claim Page SSO - way to login to Claim Page with access token using single sign on.
To enter Claim Page without login it is needed to use URL with following format:
https://<claimPageURL>/<tenant>/login?userGlobalId=<userID>&redirectUrl=<redirectUrl>&sso_token=<ssoToken>
For production enviroment:
https://myclaim.scalepoint.com/<tenant>/login?userGlobalId=<userID>&redirectUrl=<redirectUrl>&sso_token=<ssoToken>
Parameter name | Description | Example |
---|---|---|
<tenant> |
Tenant name | codan, tryg, nemforsiking etc. |
<userID> |
User identifier - please see section below - UserId | 11111111-1111-1111-1111-111111111111@tenant.scalepoint.com |
<redirectUrl> |
URL to claim page where user wants to enter | claims/1/overview |
<ssoToken> |
Access token from authorization server - please see section below - SSOToken | aa0a92f77f0cef715d2f634e3b5def9e |
UserId is a combination of agentId
and tenantName
in following format: <agentId>@<tenant>.scalepoint.com
11111111-1111-1111-1111-111111111111@tenant.scalepoint.com
It can be obtained on Participants tab in Claim details in CWA. Please check Access to claim page link - contextUserGlobalId
is a value that we are searching for.
To receive SSO Token, autorization server need to be used. Please refer to the documentation about details of authentication process.
Parameter name | Description | Example |
---|---|---|
scope |
Requested scope | self-service:sso |
client_id |
Client identifier | <tenant>_cp_sso |
client_secret |
Self-signed X.509 certificate (2048 bit RSA) with private key. | |
grant_type |
Client credentials flow | urn:scalepoint:params:oauth:grant-type:resource-scoped-access |
target |
URL address that need to be authenticated - URL from first section without ssoToken param | https://<claimPageURL>/<tenant>/login?userGlobalId=<userID>&redirectUrl=<redirectUrl> |
client_assertion_type |
JWT Bearer token assertion type | urn:ietf:params:oauth:client-assertion-type:jwt-bearer |
If request succeeded, the token endpoint will return HTTP status 200 OK and a JSON body similar to this:
{
"access_token":"aa0a92f77f0cef715d2f634e3b5def9e",
"expires_in":300,
"token_type":"Bearer"
}
access_token
can be used as SSO Token