Validate access and ID tokens
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Validate access and ID tokens
Description
Validates access and ID tokens. Opaque tokens must use remote validation. Non-opaque tokens can also use remote validation to verify that a user is still active. Remote validation requests must include the base64-encoded values for unique client ID and a client secret in the authorization header. OESECTOOL does not support generating opaque tokens. For remote validation tests, use a non-opaque token.
HTTP Operation
POST
URL
|
The request to the server must include the base64-encoded values for
general.cid:general.client_secret.
Command-line example
For example, if general.cid=oeablClient and
general.client_secret=oesectoolsecret the authorization code is
'b2VhYmxDbGllbnQ6b2VzZWN0b29sc2VjcmV0'
|
Note: This command was reformatted to fit the
page.
Result
A JSON string with a set of public keys:
|
Note: This output was reformatted to
fit the page.
If the token is inactive, the output is:
|