Error codes
- Kristoffer Kristoffer (Unlicensed)
- Jan Åge Lavik
Contents
Introduction
This page contains an overview of possible error codes that may be displayed to end-users during usage of the BankID OpenID Connect provider. The document is intended for the development and support organizations of banks and merchants helping to deal with customer incidents.
The error codes are grouped according to their source of origin, and are divided into a set of categories. Note that the collection of error codes presented by this service is a combination of
- special error codes associated to this OpenID Connect provider
- common BankID error codes originating in the common BankID components and infrastructure
Overview
Error codes are grouped according to their source of origin and/or type of error based on the first digit(s) of the error code.
| Prefix | Description |
|---|---|
| D or no prefix | Errors originating in the OIDC web client or related to the OIDC platform in general |
| C | Errors related to BankID on mobile |
| S | Errors related to signing |
Categories
Errors are divided into the following categories. Each category has an associated multi purpose error message to the end user.
| ID | Category | End user message | Actions available |
|---|---|---|---|
| 1_GEN | Generic | Det har oppstått en feil Vennligst prøv igjen. Skulle feilen vedvare, ta kontakt med banken som har utstedt din BankID og oppgi følgende kode: OIDC-$ An error has occurred Please try again. If the error continues to occur, please contact the bank that has issued your BankID and refer to the following code: OIDC-$ | Shows a button that tries to reset the error state and re-start the session. |
| 2_API | API error Errors related to API returning error or bad data | Det har oppstått en feil Ta kontakt med banken som har utstedt din BankID, og oppgi følgende kode: OIDC-$. An error has occurred Please contact the bank that has issued your BankID, and refer to the following code: OIDC-$. | Shows a button that tries to reset the error state and re-start the session. |
| 3_COM | Communication error Error connecting to API, networking issues | Det har oppstått en kommunikasjonsfeil Dersom feilen vedvarer ta kontakt med banken som har utstedt din BankID og oppgi feilkode OIDC-$. A communication error has occured. If the error continues to occur, please contact the bank that has issued your BankID, and refer to the following code: OIDC-$. | Shows a button that tries to reset the error state and re-start the session. |
| 4_BIMIN | BIM initialization error Error while initializing BankID on mobile | En prosess finnes fra før. A process is already running. | Shows a button that tries to reset the error state and re-start the session. |
| 5_BIMREF | BIM reference error Error during BankID on mobile reference step | Det har oppstått et tidsavbrudd A timeout has occurred. | Shows a button that tries to reset the error state and re-start the session. |
6_UNREC | Unrecoverable error Error shown after getting into an unrecoverable error state | En feil har oppstått An error has occurred | Shows a button that will cancel the session and try to redirect to cancellation endpoint. |
| 7_SKIP | Unrecoverable error (skip) Returns to cancel authentication immediately due to critical error | None. User is immediately redirected back to cancelAuth endpoint. | |
| 9_CAS | Cookie Activation Service | None. User is immediately redirected back to cancelAuth endpoint. |
Error codes
no prefix - errors related to OIDC
| Code | Category | Description | Action/solution |
|---|---|---|---|
| 4096 | 1_GEN | Unexpected script error | Contact BankID support. |
| 4097 | 1_GEN | Occurs if phone number or birthdate is unexpectedly missing after input validation before initializing SIGNBIM. | Invalid phone number or birthdate. If the problem persists, contact BankID support. |
| 4098 | 1_GEN | No IDP has been selected for mobile (BIM/SIGNBIM) | Contact BankID support. |
| 4099 | 1_GEN | Invalid IDP selected for mobile (BIM/SIGNBIM) | Contact BankID support. |
| 4100 | 1_GEN | Method selected, but the IDP argument is missing | Contact BankID support. |
| 4101 | 1_GEN | Failed to get session when handling error from IDP during initialization | Contact BankID support. |
| 1200 | 1_GEN | BID helper did not load | Problem loading BankID client. Contact BankID support. |
| 1201 | 1_GEN | BID callback gave error | Problem with BankID client. Contact BankID support. |
| 1202 | 1_GEN | BID callback missing result | Problem with BankID client. Contact BankID support. |
| 1203 | 1_GEN | BID callback status error | Problem with BankID client. Contact BankID support. |
| 1204 | 1_GEN | BID helper did not load within a reasonable time | Problem with BankID client. Contact BankID support. |
| 1205 | 1_GEN | BID helper url missing | Problem with BankID client. Contact BankID support. |
| 14003 | 2_API | Composite-idp could not communicate with SDM server | Problem with BankID client. Contact BankID support. |
| 4096 | 9_CAS | Generic error | Contact BankID support. |
| 4097 | 9_CAS | Could not open set cookie window from iframe | Contact BankID support. |
| 4098 | 9_CAS | Could not set cookie in set cookie window | Contact BankID support. |
| 4099 | 9_CAS | Sending event log took to long (never sent to server) | Contact BankID support. |
| 4100 | 9_CAS | User exists client without finishing session | Contact BankID support. |
| 4101 | 9_CAS | Set Cookie Window is opened and it's not in correct state | Contact BankID support. |
D - errors related to OIDC
| Code | Category | Description | Action/solution |
|---|---|---|---|
| D010 | 1_GEN | API request api/session/{sid}/removeError failed - Likely communication error | Contact BankID support. |
| D011 | 1_GEN | API request for generic IDP failed - Likely communication error | Problem connecting to identity provider. Try another authentication method or contact BankID support. |
| D108 | 1_GEN | API request /api/session/{sid}/removeError returned error | Contact BankID support. |
| D112 | 1_GEN | Generic IDP request returned error | Problem connecting to identity provider. Try another authentication method or contact BankID support. |
| D103 | 2_API | API request /api/session/{sid} responded with error | Problem with user session. Contact BankID support. |
| D104 | 2_API | API request /api/bim/initialize responded with error | Problem with BankID on mobile. Contact BankID support. |
| D105 | 2_API | API request /api/bid/initialize responded with error | Problem with BankID. Contact BankID support. |
| D106 | 2_API | API request /api/bim/initialize returned error and /api/session/{sid} did not give errorCode | Problem with BankID on mobile. Contact BankID support. |
| D107 | 2_API | API request /api/bid/initialize returned error and /api/session/{sid} did not give errorCode | Problem with BankID. Contact BankID support. |
| D114 | 2_API | API request /api/signbim/initialize responded with error | Problem with signing on BankID on mobile. Contact BankID support. |
| D116 | 2_API | API request /api/signbim/initialize returned error and /api/session/{sid} did not give errorCode | Problem with singing on BankID on mobile. Contact BankID support. |
| D200 | 5_BIMREF | BIM polling timed out, answer was not received within the time frame given | BankID on mobile did not receive an answer in time. |
| D210 | 5_BIMREF | SIGNBIM polling timed out, answer was not received within the time frame given | Signing with BankID on mobile did not receive an answer in time. |
| D002 | 3_COM | API request /api/session failed - Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D003 | 3_COM | API request /api/bim/initialize failed - Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D004 | 3_COM | Both api/bim/initialize and api/session/{sid} failed - Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D007 | 3_COM | API request api/bid/initialize failed - Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D008 | 3_COM | API request api/cancelAuth failed - Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D009 | 3_COM | API request api/bid/initialize and api/session/{sid} failed - Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D013 | 3_COM | API request /api/signbim/initialize failed - Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D014 | 3_COM | Both api/signbim/initialize and api/session/{sid} failed - Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D000 | 6_UNREC | No legal action provided from composite-idp | Contact BankID support. |
| D005 | 6_UNREC | API request /api/bim/cancel failed | Error while user tried to cancel session. |
| D015 | 6_UNREC | API request /api/signbim/cancel failed | Error while user tried to cancel session. |
| D109 | 6_UNREC | API request /api/bim/cancel responded with error | Error while user tried to cancel session. |
| D119 | 6_UNREC | API request /api/signbim/cancel responded with error | Error while user tried to cancel session. |
| D001 | 7_SKIP | Session could not be found by composite-idp | Problem with authentication session. Session aborted. |
| D300 | 7_SKIP | No sid provided from composite-idp | Session not found. |
C - errors related to BankID on mobile
| Code | Category | Description |
|---|---|---|
| C293 | 4_BIMIN | Another BankID on Mobile session has already started towards the same phone number. |
| C131 | 4_BIMIN | A process is already running at this telephone number. |
| C302 | 5_BIMREF | Timeout from the mobile service provider. |
| C* | 1_GEN | Any other BIM related error. |
S - errors related to BankID signing
| Code | Category | Description | Action/solution |
|---|---|---|---|
| S100 | 1_GEN | Cannot start signing, order not found | Cannot find signing order. Make sure that documents are uploaded and signing order is embedded with the authentication request. |