In case of an error, the /users/{userID@domain/login} endpoint responds with an HTTP 409 response code, and provides an error and a message field in the reply JSON body.
The following values are possible for the error and message fields:
Possible error and message values | ||
Status | Error type | Message |
|---|---|---|
409 | Conflict | Authentication failed |
409 | Conflict | User is disabled |
409 | Conflict | User is locked |
409 | Conflict | Invalid Request ID |
409 | Conflict | Request ID is invalid |
409 | Conflict | User refused |
409 | Conflict | Registration ceremony was not started |
409 | Conflict | Message not sent. Gateway exited with error and reported: invalid_destination. |
409 | Conflict | Timed out |
409 | Conflict | Gateway exited with error |
409 | Conflict | Failed to send push notification. No applicable digipass found. Instance should have both a PNID and a secure channel set. |
409 | Conflict | User is disabled. |
409 | Conflict | UAF 1.1: Unacceptable Content. There was a problem with the contents of the message and the server was unwilling or unable to process it. |
409 | Conflict | UAF 1.1: The server refused to service the request because the request message nonce was unknown, expired or the server has previously serviced a message with the same nonce and user ID. |