UI displays a misleading error message when the OIDC provider is unreachable. #203

New issue

Closed

opened 2026-09-07 16:42:09 +00:00 by aaperis · 0 comments

aaperis commented

2026-09-07 16:42:09 +00:00

(Migrated from github.com)

Describe the bug

When LSAAI is down or unreachable the user is presented with "Try signing in with a different account." and on the webapp side the error is logged as:

[next-auth][error][SIGNIN_OAUTH_ERROR] 
frontend-1  | https://next-auth.js.org/errors#signin_oauth_error getaddrinfo ENOTFOUND host.docker.internal {
frontend-1  |   error: {
frontend-1  |     message: 'getaddrinfo ENOTFOUND host.docker.internal',
frontend-1  |     stack: 'Error: getaddrinfo ENOTFOUND host.docker.internal\n' +
frontend-1  |       '    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26)',
frontend-1  |     name: 'Error'
frontend-1  |   },
frontend-1  |   providerId: 'lsaai-oidc',
frontend-1  |   message: 'getaddrinfo ENOTFOUND host.docker.internal'
frontend-1  | }

Steps to reproduce

Do not start the sda-dev stack but only the production sdad:

./compose-prod.sh up --build

Then try to Sign-in. Watch the logs.

Expected behavior

A user friendly, suitable message is displayed to the user when ENOTFOUND error is captured (something like "LSAAI is unavailable should be sufficient)".
Tests verifying the fix are added

## Describe the bug When LSAAI is down or unreachable the user is presented with "Try signing in with a different account." and on the webapp side the error is logged as: ``` [next-auth][error][SIGNIN_OAUTH_ERROR] frontend-1 | https://next-auth.js.org/errors#signin_oauth_error getaddrinfo ENOTFOUND host.docker.internal { frontend-1 | error: { frontend-1 | message: 'getaddrinfo ENOTFOUND host.docker.internal', frontend-1 | stack: 'Error: getaddrinfo ENOTFOUND host.docker.internal\n' + frontend-1 | ' at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26)', frontend-1 | name: 'Error' frontend-1 | }, frontend-1 | providerId: 'lsaai-oidc', frontend-1 | message: 'getaddrinfo ENOTFOUND host.docker.internal' frontend-1 | } ``` ## Steps to reproduce Do not start the sda-dev stack but only the production sdad: ``` ./compose-prod.sh up --build ``` Then try to Sign-in. Watch the logs. ## Expected behavior - [ ] A user friendly, suitable message is displayed to the user when `ENOTFOUND` error is captured (something like "LSAAI is unavailable should be sufficient)". - [ ] Tests verifying the fix are added