...
When specifying a resource uri data source, you will have to can select which authentication method is used for query parameter for authentication should be added to the resource URI . Please call.
If an authentication based on a query parameter is required, select the appropriate one based on your identity provider's manual.
If the manual doesn't provide clear instructions, or when you are implementing an OIDC compliant authentication on a /userinfo endpoint, select "bearer" (see also: RFC 6750).
Also, whenever the token endpoint (!) returned that the token is a bearer token, the "Authorization: Bearer (token)" header is added to the resource URI calls.
In case the first call returns an HTTP Error response, another call without the query parameter (but with the token still in the Authorization header) is invoked as fallback strategy.
| Value | Authentication |
|---|---|
| oauth_token | The resource URI will be called as HTTP GET call, with a query parameter 'oauth_token' |
| oauth2_access_token | The resource URI will be called as HTTP GET call, with a query parameter 'oauth2_access_token' |
| access_token | The resource URI will be called as HTTP GET call, with a query parameter 'access_token' |
| bearer | The resource URI will be called as HTTP GET call, with an with a query parameter 'bearer' (and typically with Authorization header of type Bearer & the token - see above) |
| Info |
|---|
All data retrieved via resource uri will be stored in the audit trail. You can find more information about the audit trail in the section below. |
...