Step 17: Token Introspection
POST {{authPath}}/{{envID}}/as/introspect
You can use the POST /{{envID}}/flows/{{flowID}}
endpoint operation to examine the token to verify that the aud
(audience property) and scope
properties specify the new custom resource and custom scope, respectively.
For more information about token introspection for access tokens, see Token Introspection (Access Token) in the PingOne Platform API Reference.
Request Body
[{"name"=>"token", "value"=>"{{customResourceAccessToken}}", "datatype"=>"string"}, {"name"=>"client_id", "value"=>"{{appID}}", "datatype"=>"string"}, {"name"=>"client_secret", "value"=>"{{appSecret}}", "datatype"=>"string"}]
HEADERS
Key | Datatype | Required | Description |
---|---|---|---|
Authorization | string | ||
Content-Type | string |