Configuring introspection for a native OAuth provider
Define an introspection path to allow the metadata for an access token to be examined.
About this task
Token introspection allows an authorized holder of an access token to examine the contents of tokens using an introspection path. The access token to introspect must be obtained through the native OAuth provider. Introspection provides context for the token by allowing an authorized protected resource to query the authorization server to determine the set of metadata for a given token. The metadata includes whether or not the token is currently active, the scopes assigned to the token, and the authorization context in which the token was granted (including who authorized the token and which client it was issued to). API Connect token introspection conforms to IETF RFC 7662. See OAuth 2.0 Token Introspection.
One of the following roles is required to enable introspection for a native OAuth Provider:
- Topology Administrator
- Custom role with the Settings:Manage permissions
You can select the introspection settings page for a native OAuth provider immediately on completion of the creation operation detailed in Configuring a native OAuth provider, or you can update the introspection settings for an existing native OAuth provider. If you want to update the introspection settings for an existing native OAuth provider, complete the following steps before following the procedure described in this topic:
- Click .
- Select the required native OAuth provider.
Perform the following steps to enable introspection:
- Click Introspection in the sidebar menu.
- Select the check box to enable Introspection. The OAuth standard path for introspection, /oauth2/introspect is automatically entered. This path will be used when another entity inspects the token contents.
- Click Save when done.