# Contact support

Stuck? Our experts are available to help Signicat customers with technical issues.

Email Signicat Technical Support
support@signicat.com

Alternatively, you can check out our community forum (opens new window) for answers to commonly asked questions as well.

# Error codes

If you have encountered an error code, check the table below for more detailed information. Encountered an error code not on the list? Contact Support for help.

# Broker error codes

Error code Name Description
invalid_account_id Invalid Account ID Error An accountId is sent as part of api calls and 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_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 sesssion.
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 sesssion.
session_error Session Error This is a quite generic error that happens in different Signicat components, such as the Broker for various reasons. Among possible reasons, the most commonly occurring ones are:
1) User session expires due to inactivity on pages of interaction.
2) Publicly available endpoints are called with wrong or unexpected session state; e.g. 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

errorCode title httpStatus detailsTemplate description
AGW-1000 The state was not provided. 404 Missing session.
AGW-1100 The state was not found. 404
AGW-2000 The client doesn't exist. 404
AGW-2100 Billing not configured. 404
AGW-3000 Auth Gateway Error. 404 An error was occurred while requesting the authentication.
AGW-3100 Auth Gateway session not complete. 404
AGW-3200 The authentication was aborted. 404 A message informing that the Authentication was aborted was received from IdP.
AUS-1100 Client not found. 404 Client with ID {clientId} does not exist. Ensure your ID is correct. The client may have been deleted.
AUS-1101 Client already exists. 409 Client with ID {clientId} already exists.
AUS-1110 Client secret not found. 404 Secret with ID {secretId} does not exist on client with ID {clientId}. Ensure your IDs are correct. The secret may have been deleted, or it may belong to a different client.
AUS-1120 Public key not found. 404 Public key {keyId} does not exist on client with ID {clientId}. Ensure your IDs are correct. The key may have been deleted, or it may belong to a different client.
AUS-1129 Public Key In Use. 400 Key with ID {keyId} can not be removed because it is the only key on Client with ID {clientId} which requires an encryption key The client is configured to encrypt the ID token and/or the UserInfo response. Removing the last encryption key would put the client in an invalid state. Configure the client to not encrypt ID tokens and UserInfo responses before removing the final encryption key.
AUS-1130 Requested Client revision was not found. 404 The Client with ID {clientId} does not have a revision with version {version}.
AUS-1140 Client custom claim not found. 404 Custom claim with ID {customClaimId} does not exist on client with ID {clientId}. Ensure your IDs are correct. The custom claim may have been deleted, or it may belong to a different client.
AUS-1200 API not found. 404 API with ID {apiId} does not exist. Ensure your ID is correct. The API may have been deleted.
AUS-1201 API already exists. 409 API with ID {apiId} already exists.
AUS-1210 API secret not found. 404 Secret with ID {secretId} does not exist on API with ID {apiId}. Ensure your IDs are correct. The secret may have been deleted, or it may belong to a different API.
AUS-1230 Requested API revision was not found. 404 The API with ID {apiId} does not have a revision with version {version}.
AUS-1990 Account not found. 404 Account with ID {accountId} does not exist. Ensure your ID is correct. The account may have been deleted.
AUS-1991 Account already exists. 409 Account with ID {accountId} already exists.
AUS-1993 Version Mismatch. 412 The resource version does not match any of the requested versions.
CFG-1000 Client is not configured properly to use encryption. 400 The Client is not configured properly to use encryption. Client needs to be configured with: 'EncryptIdTokens=true' and 'UserInfoResponseType=Encrypted or SignedAndEncrypted'
ERR-4000 Provided data is invalid. 400 See the 'validationErrors' field for specific error messages. The HTTP request contained missing or invalid data. The response body will contain detailed information about what parts of the input were wrong or missing. Consult the API documentation for additional information.
ERR-4001 Authentication required. 401 This operation requires authentication.
ERR-4003 Authorisation required. 403 You do not have access to perform this operation.
ERR-4004 Path does not match any endpoints. 404 The path '{path}' does not match any endpoints. Ensure your URI is shaped according to the API documentation.
ERR-5000 An error occurred. 500 An unexpected error occurred. Please try again later or contact support. This is a generic error code which may be displayed when one of the following conditions are met:
1. Disclosing specific information may not help the end-user solve or understand the problem.
2. Disclosing specific information may pose a security risk.
3. An error code has not been defined for the error.
The issue may be temporary, allowing the end-user to retry, or it may require the end-user to contact support.
ERR-5001 Error code not found. 404 The error code {errorCode} does not exist.
IDP-1000 Unsuccessful Response 500 Unsuccessful response was received from IdP.
IDP-2000 Invalid Login Response. 500 An Invalid Login Response was received from IdP.
IDP-3100 The authentication is pending. 500 A message informing that the Authentication is pending was received from IdP.
IDP-3200 The authentication was aborted. 500 A message informing that the Authentication was aborted was received from IdP.
IDP-3300 The authentication has failed. 500 A message informing that the Authentication has failed was received from IdP.
IDP-4000 Unserialisable Login Request Result. 500 An Unserialisable Login Request Result was received from IdP.
IDP-4100 Invalid Login Request Result. 500 An Invalid Login Request Result was received from IdP.

# Return to configuration

Initial setup instructions
Return to the main configuration section of the documentation to help you to integrate with Signicat's products.
Last updated: 21/03/2023 12:33 UTC