OAuth 2 clients must be registered with SSO management application to enable OAuth integration. During registration JSON formatted client metadata is exchanged with SSO management.
...
Anchor |
---|
...
|
http://openid.net/specs/openid-connect-registration-1_0.html#RegistrationRequest
https://tools.ietf.org/html/rfc7591#section-3.1
Parameters
...
Code Block | ||||
---|---|---|---|---|
| ||||
{ "redirect_uris": [ "https://client.example.com/response" ], "grant_types": [ "authorization_code" ] } |
Anchor | ||||
---|---|---|---|---|
|
http://openid.net/specs/openid-connect-registration-1_0.html#RegistrationResponse
https://tools.ietf.org/html/rfc7591#section-3.2
Parameters
...
Code Block | ||||
---|---|---|---|---|
| ||||
{ "redirect_uris": [ "https://client.example.com/response" ], "grant_types": [ "authorization_code" ], "client_id": "2001221477", "client_secret": "***" } |
OAuth API Requests with Client Identifier and Secret
OAuth API requests such as 4512350299 and TokenInfo Request require Access Token Request at Authorization code grant and web single sign-on and Token Introspection at Authorization code grant and native applications require client_id and client_secret as input.
...