Authenticates the user in the DPS by using a PAT (Personal Access Token) instead of username and password.
This is the recommended way to authenticate machine-to-machine integrations, since it does not require handling the end-user password and the token can be revoked without changing the user credentials.
The payload must provide both the pat and the apiKey identifying the client application, while the tenant is identified by the X-Servitly-Tenant header.
The response is the same returned by the credentials-based login: the JWT token, its expiration and the data needed to renew it.
The name of the tenant (e.g. acme).
The login PAT and API Key.
The payload message for login requests based on PAT.
The API KEY identifying the client.
The PAT used for login.
Authentication succeeded.
The response message for login requests.
The JWT token to include as the bearer token in authenticated requests.
The timestamp when the token will expire and must be refreshed.
Generally one hour after issuance, but this may vary over time.
The refresh token used to request a new JWT token when the current one expires.
The id of the authenticated user.
The id of the tenant.
Invalid credentials, user not authenticated.
The error response.
Internal server error.
The error response.