Error codes
When an error occurs, you will receive an error message with an error code. If you have encountered an error, check the following tables for additional information.
If you encounter an error and require assistance, you can contact us by creating a support ticket in the Signicat Dashboard.
Alternatively, you can check out our community forum for answers to commonly asked questions.
Broker error codes
When you use the Signicat eID Hub and there is an error in our broker service, you can find the error report in the Dashboard eID Hub > Message Log. The following table provides additional information on the errors.
| Error code | Name | Description |
|---|---|---|
invalid_account_id | Invalid Account ID Error | An accountId is sent as part of API calls. This error indicates that an unexpected accountId was sent in the request. |
invalid_redirect_url | Invalid Redirect URL Error | Internal API calls often have a response with a redirectUrl. This error indicates that an unexpected redirectUrl was received by one of the components. |
invalid_pushback_url | Invalid PushBack URL Error | In the headless flow a pushBackUrl may be provided in the request (optional). This error indicates that an invalid pushBackUrl was received by one of the components. |
invalid_message_id | Invalid Message Id Error | A messageId is sent as part of API calls and this error indicates that a service received a messageId it doesn't know about or did not expect for the current user session. |
invalid_transaction_id | Invalid Transaction Id Error | A transactionId is sent as part of API calls and this error indicates that a service received a transactionId it doesn't know about or did not expect for the current user session. |
session_error | Session Error | This is a quite generic error that happens in different Signicat components, such as the Broker, for various reasons. The most common causes are: 1) User session expires due to inactivity on pages of interaction. 2) Publicly available endpoints are called with wrong or unexpected session state; for example, if you call a SAML ACS endpoint without first instantiating a login session from an SP you will get a Session Error. |
transaction_id_or_message_id_replayed | Replay Error | The error indicates that a Signicat component such as the Broker is trying to instantiate a login session with a messageId or a transactionId that was used recently. |
invalid_token | Token Validation Error | The error indicates that an API call was made with an invalid authorization token. A token can be invalid if: 1) It does not have correct signature. 2) It is expired. 3) It does not have correct permissions to perform the necessary operation. |
unexpected_error | Unexpected Error | This error indicates that something unexpected happened at a Signicat service and it is not handled properly one way or another. This error will usually be accompanied by an HTTP response with status 500. |
OIDC authentication error codes
When you make a call to the authorization endpoint and there is an error, you will receive a response with an error code. The following table shows additional information to help you understand what happened.
You can learn more about error codes in the documentation for OIDC implementation.