Third Party oAuth Providers
A third party provides the OAuth token presented by a client application. API Connect must determine if the token is valid and either allow or disallow API access.
![]() |
Add caption |
The exchange proceeds as follows.
1. The client application requests an OAuth token from the third party OAuth provider. The provider requires credentials from the client, which are validated by the third party provider. The client obtains a token.
2. The client application sends an API access request to an endpoint managed by API Connect. This request must contain the OAuth token and an API Connect Application ID (and perhaps an optional Secret). API Connect Application ID is used to identify the application to API Connection, it is used for quota enforcement and optional auditing.
The application can provide the credential that APIc needs for 3rd party OAuth provider, by including an x-introspect-basic-authorization header in the request.
If the client does not have a valid API Connect Client ID, it may be necessary to use an intermediary utility to provide this credential. This intermediary could be a script running on API Connect.
3. API Connect must verify the OAuth token. API Connect can take one of two possible actions.
a. if the OAuth token is in JSON Web Token format, API Connect can utilize JWT Validate policy to verify the access token
b. if the OAuth token is an opaque token format, API Connect can contact the issuing third party OAuth provider to verify the token
a. if the OAuth token is in JSON Web Token format, API Connect can utilize JWT Validate policy to verify the access token
b. if the OAuth token is an opaque token format, API Connect can contact the issuing third party OAuth provider to verify the token
Comments
Post a Comment