Troubleshoot DigiD integration & DigiD Error Codes
When the DigiD integration seems to fail, you need to enable logging on the category "Digid" and maxlevel set to (at least) 5 to find out what's the exact reason why it's failing.
Then, within the log file (or other log destination), you need to search for a message containing "authentication initialization result". Inspect this result, which is something like "a-select-server=digidas1&result_code=0099". It is the result_code which refers to the reason for failing.
The table below lists these result codes.
| result_code | Description |
|---|---|
| 0000 | No error. This is the default result_code when the authentication succeeds. |
| 0001 | DigiD is temporarily out of order. |
| 0003 | DigiD can not process the request. DigiD is temporarily out of order. |
| 0004 |
The authentication verification failed because of invalid DigiD credentials. Usually, this occurs when an incorrect syntax for the verification request is used. |
| 0007 |
The authentication verification failed because of invalid DigiD credentials. Usually, this occurs when an incorrect syntax for the verification request is used. |
| 0030 | Invalid request. The request is unknown or contains an syntax error. |
| 0032 | The specified app_url parameter is invalid. |
| 0033 | The specified a-select-server parameter is invalid. |
| 0040 | The user has aborted the authentication process. |
| 0050 | DigiD is too busy. DigiD does have too many authentication sessions to process. |
| 0070 | Invalid session; the session does not exists with DigiD. |
| 0080 | The "Webdienst" is not yet active or not active anymore. DigiD may only be used by "Webdiensten" marked as active. |
| 0099 |
The "Webdienst" is not authorized. The parameter shared_secret passed to DigiD doesn't correspond with the agreed authentication code for your "Webdienst". This result_code is also returned when the passed app_id parameter is unknown or not bound to your "Webdienst". |
| 010c | DigiD is temporarily out of order. |