SSO stopped working

[andreasdueren]

upon boot it throws this error: WARN: Missing driver definition for "openid" auth provider.

I didn't change anything in my settings, something seems to have changed during an upgrade.

[andreasdueren]

I changed the .env from OKTA to GOOGLE. Now the login process works but won't let me in and throws this error: WARN: Invalid user credentials

and

GET /auth/login/google/callback?code=NzHUmE6u0fq4968yHI05fCP2HNKPboK4yeQPL3uwcBJ&state=GKMfkPqtFUG5VB0vrKOL1Cz4sKL0j4xcb3bPfZxqCXM&iss=https%3A%2F%2Fmy.tld.dm%2Fopenid 302 515ms
GET /admin/login?reason=SERVICE_UNAVAILABLE 200 1ms

[andreasdueren]

 -
 - ╰───────────────────────────────────────────────────╯
 - │ https://github.com/directus/directus/releases │
 - │ 1 version behind │
 - │ 11.2.1 → 11.2.2 │
 - │ │
 - │ │
 - │ │
at AuthenticationService.login (file:///app/code/node_modules/@directus/api/dist/services/authentication.js:81:19)
DirectusError: Invalid user credentials.
"code": "INVALID_CREDENTIALS",
"message": "Invalid user credentials.",
"name": "DirectusError",
"stack":
"status": 401
"type": "",
err: {
}
at async file:///app/code/node_modules/@directus/api/dist/auth/drivers/openid.js:302:28
DirectusError: Invalid user credentials.
"code": "INVALID_CREDENTIALS",
"message": "Invalid user credentials.",
"name": "DirectusError",
"stack":
"status": 401
"type": "",
err: {
}
at AuthenticationService.login (file:///app/code/node_modules/@directus/api/dist/services/authentication.js:81:19)
at async file:///app/code/node_modules/@directus/api/dist/auth/drivers/openid.js:302:28
"code": "INVALID_CREDENTIALS",
"message": "Invalid user credentials.",
"name": "DirectusError",
"stack":
"status": 401
"type": "",
err: {
}

[msbt]

https://forum.cloudron.io/topic/12817/oidc-login-broken-with-8-1-0-update/7?_=1732142838325

[joseph]

@andreasdueren yes, this was a regression in 8.1. https://git.cloudron.io/platform/box/-/commit/16fa3390252e29f1803a18990c7b104817fa4d9f is the fix

[joseph]

https://forum.cloudron.io/topic/12817/oidc-login-broken-with-8-1-0-update/8 has info on how to apply the fix