OAuth 2 Authorization
Collibra REST API authentication with Basic HTTP Authentication (RFC 7617).
As specified in
Section 2.3.1 of RFC 6749, the client identifier is
encoded using the application/x-www-form-urlencoded encoding algorithm, and the encoded value is used as
the username; the client secret is encoded using the same algorithm and used as the password.
For example, the client ID urn:sys:env:2eeadf60-1a11-5170-7e57-000000000000:i:1cnxtsn is URL-encoded to
urn%3Asys%3Aenv%3A2eeadf60-1a11-5170-7e57-000000000000%3Ai%3A1cnxtsn, and this can be set as username.
Type of authorization. The only supported grant type is client_credentials.
Token successfully generated.
The Base64 encoded access token.
The type of access token returned. The only supported type is "Bearer".
The scopes that have been granted for the client.
This field is omitted if the client did not request any specific scopes, in which case the default scopes for the client will have been granted.
The time in seconds until the access token is no longer valid.
The token request was invalid.
The client credentials are invalid.
Last updated
Was this helpful?