This documentation supports the 20.02 version of Remedy Single Sign-On.

To view an earlier version, select the version from the Product version menu.

Developing

Remedy Single Sign-On provides the following OAuth 2.0 endpoints:

/rsso/oauth2/v1.1/token

Issues the access/refresh tokens. Additionally, this endpoint supports JWT as Authorization Grant Open link , returns the token_type parameter in the response, and may use JWT for Client Authentication Open link . For more information, see Token Endpoint Open link .

/rsso/oauth2/token

Issues the access/refresh tokens. Additionally, this endpoint supports JWT as Authorization Grant Open link and may use JWT for Client authentication Open link . For more information, see Token Endpoint Open link .

/rsso/oauth2/authorize

Obtains the OAuth2 authorization code. For more information, see Authorization Endpoint Open link .

/rsso/oauth2/revoke

Enables Remedy SSO to invalidate its tokens if the end user logs out or changes identity. Additionally, this endpoint may use JWT for Client authentication Open link . For more information, see Revocation Endpoint Open link .

/rsso/oauth2/introspect

Enables Remedy SSO to check the validity of access tokens, an obtain meta-information such as which end user and which scopes are associated with the token. Additionally, this endpoint may use JWT for Client authentication Open link . For more information, see Introspection Endpoint Open link .

/rsso/oauth2/userinfo

Retrieves the consented UserInfo and other claims about the logged-in end user in Remedy SSO. For more information, see UserInfo Endpoint Open link .

/rsso/oauth2/jwks

Returns information about the JWK Set for the specified OAuth provider. For more information, see JWKS Endpoint Open link .

/rsso/.well-known/openid-configuration

Retrieves the OpenID Connect provider's configuration information. For more information, see OpenID Connect Configuration Endpoint Open link



Was this page helpful? Yes No Submitting... Thank you

Comments