Frends.OAuth.ParseToken / 1.3.0
Summary
Validates an incoming JWT or Authorization header — signature, issuer, audience and lifetime — against signing keys fetched from a discovery endpoint or supplied directly, and returns the claims it carries.
Typical use — authorising callers of a Frends API, where the returned claims are what a Process makes its access decisions on
Input parameters.
| Name | Type | Default | Example | Description |
|---|---|---|---|---|
| AuthHeaderOrToken | String |
#trigger.data.httpHeaders["Authorization"] |
#trigger.data.httpHeaders[\"Authorization\"] |
Either the JWT token or the Authorization header value through #trigger.data.httpHeaders["Authorization"]. |
| Audience | String |
– | fIVLouKUZasdYP3tdO9D3dwd6ZNS9Be |
The expected Audiences of the token, e.g. ClientId. |
| Issuer | String |
https://xyz.eu.auth0.com/ |
https://xyz.eu.auth0.com/ |
The expected Issuer of the token. |
| ConfigurationSource | ConfigurationSource |
Static |
Static |
The configuration source. Possible values:
|
| WellKnownConfigurationUrl | String |
https://xyz.eu.auth0.com/.well-known/openid-configuration |
https://xyz.eu.auth0.com/.well-known/openid-configuration |
The URL where the .well-known configuration for the issuer is located. |
| StaticJwksConfiguration | String |
– | o80vbR0ZfMhjZWfqwPUGNkcIeUcweFyzB2S2T |
Static signing keys to use, can be found in the jwks_uri from the .well-known openid-configurations. |