Single Sign On URL
Learn how to generate a URL for the hosted UI used for Single Sign On (SSO) of license users with the /api/v4/sso_url endpoint.
Endpoint
Method:
GETPath:
/api/v4/sso_urlDescription: Returns the Single Sign-On URL for license user authorization.
Authentication
Required headers
Date(string)Authorization(string)
Recommended headers
Accept: application/json
Request
Query parameters
Required:
product(string)customer_account_code(string)
Optional:
response_type(string) —codeortoken. Default:code
Example request URL: /api/v4/sso_url?product=string&customer_account_code=string
(You can add &response_type=token to enable Implicit grant, otherwise it will default
to the Authorization Code grant)
Examples
Example success response (200)
Authorization method
By default, authorization for SSO uses the Authorization Code grant which attaches a code query parameter to the redirect_uri once the user is verified. This code is then sent in the request body when doing license activation.
If you prefer to receive user pool tokens directly on the redirect, you can use the Implicit grant. In that case, user pool tokens (id_token, access_token, expires_in, and token_type) are attached to the redirect_uri (instead of code) once the user is verified, and the access_token can then be used for license activation. Be aware that this exposes user tokens in the redirect URI and results in a longer URI.
To enable Implicit grant, add response_type=token to this endpoint.
Example: /api/v4/sso_url/?customer_account_code=test&product=test&response_type=token
Schema
Errors
If an error occurs, the response will have an HTTP status code >= 400 and the response body will contain an error description in this format:
Error schema (JSON Schema)
List of exceptions
unknown_product (400): Provided product was not found
missing_headers (400): Some headers are missing
authorization_missing_params (400): Some parameters are missing in the authorization: { params }
Last updated
Was this helpful?