OIDC error codes
When you make a call to the Signicat OIDC server and an error occurs, you will receive a response with an error code. The information on this page provides more context to help you understand the cause of common errors.
If you encounter an error and require assistance, you can contact us by creating a support ticket in the Signicat Dashboard.
You can find the complete log of any error in the Signicat Dashboard > eID Hub > Audit Log.
Handling OIDC errors
We follow the OIDC and OAuth standards as closely as possible, including how we handle error messages.
Authorization errors
Errors from the /authorization endpoint are typically returned as URL parameters to the redirect URI. These parameters are:
If an error cannot be passed in the redirect URI, we display an error page instead. These errors usually result from an incorrect implementation or invalid configuration and are typically not caused by an end-user interacting with a service.
Token and userInfo errors
Errors from the token and UserInfo endpoints follow the OpenID Connect and OAuth protocol specifications:
Standard errors
Additionally, standard HTTP status error codes may be returned, including:
For a list of common OIDC error codes, see the table below.
In addition to these product-specific error codes, there are generic error codes which are applicable to all Signicat APIs. To learn about these and how the error object looks, see our generic Error codes documentation.