3.1.4. Create token using identity provider

Description

Creates a token for accessing the REST API via a custom identity provider. The user credentials must be passed in a format understood by the custom identity provider, e.g., a third-party auth token in an HTTP header. The exact format of the user credentials expected by the custom identity provider can be discovered by 'GET /access/token/identity-provider/usage'. The token returned is formatted as a JSON Web Token (JWT). The token is base64 encoded and comprised of three parts. The header, the body, and the signature. The expiration of the token is a contained within the body. The token can be used in the Authorization header in the format 'Authorization: Bearer <token>'.

Responses


HTTP Code	Description	Schema
200	successful operation	string
400	NiFi Registry was unable to complete the request because it was invalid. The request should not be retried without modification.	No Content
401	Client could not be authenticated.	No Content
409	NiFi Registry was unable to complete the request because it assumes a server state that is not valid. The NiFi Registry may not be configured to support login with customized credentials.	No Content
500	NiFi Registry was unable to complete the request because an unexpected error occurred.	No Content

Consumes

/

Produces

text/plain

Example HTTP request

Request Path

/access/token/identity-provider

Example HTTP response

Response Path


         "string"