Authenticates the user in the DPS by using personal credentials (username and password), and opens a new session.
The tenant is identified by the X-Servitly-Tenant header, while the apiKey query parameter identifies the client application performing the request.
On success the response provides the JWT token to be sent as bearer token on every subsequent authenticated call, its expiration timestamp, and the refreshToken, userId and tenantId required to renew the token once expired.
The optional devices node allows mobile clients to register the device that will receive push notifications.
For security reasons unknown users and wrong passwords are reported with the same 401 error.
The name of the tenant (e.g. acme).
The API KEY identifying the client.
The login credentials and optional device details.
The payload message for login requests.
The user registration email address.
The user private password.
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 device operating system.
The mobile device model.
The mobile platform name.
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.