Authenticates the user in the DPS through the OpenID Connect plugin.
Generally, this endpoint is called on return from the OpenID provider's authentication page. The code, state, and redirectUrl values obtained from that redirect must be provided in the payload.
Alternatively, if you already have an OpenID access token, you can log in directly by supplying the accessToken field instead. In this case the code, state, and redirectUrl fields are not required: the backend validates the access token against the User Info URL configured in the OpenID Connect plugin. If the user's identity is verified, a new token for the DPS APIs will be provided. Note that the OpenID access token is different from the token returned by this endpoint, which is the one required to make authenticated requests to the DPS backend.
The name of the tenant (e.g. acme).
The API KEY identifying the client.
The OpenID login payload.
The payload message for login requests based on OpenID.
The code, state, and redirectUrl fields are required when accessToken is not present.
Single-use short-lived authorization code returned by the OpenID provider; exchange it at the token endpoint for access tokens.
Opaque anti-CSRF value returned unchanged by the OpenID provider; must match the value stored for the session.
Callback URL where the OpenID provider redirects after authentication with the code and state; must match a pre-registered redirect URI.
The access token obtained by the OpenID provider to be used for direct login.
This field is mutually exclusive with code, state, and redirectUrl.
Details about the device on which the API client is currently running.
The unique identifier which is used to match the device among different logins.
The identifier/package-name of the mobile app used to log in (e.g. com.acme.mobile).
The device operating system.
The mobile device model.
The mobile platform name.
The information of the browser (navigator.userAgent) used to access the DPS.
The device notification identifier obtained from the platform provider during the device registration for notifications.
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.