#Update from 2023.10.6 to 2024.4.2 broke OIDC

1 messages · Page 1 of 1 (latest)

serene valley
#

Hi,
I've been using Authentik for a while on my AWS LoadBalancer to protect my services with an OIDC Authentication. I updated to 2024.4.2 but now all my services show a 500 error. If I look at my logs I see a lot of Refresh token is revoked and Suspicious request. Not sure what to do here. I tried to enable offline_access in authentik but it didn't help.
Any idea ? Thanks!

#

I saw this in the changelog but really not sure what do to with this :/

The OAuth2 provider ships with a new default scope called offline_access, which must be requested by applications that need a refresh token. Previously, authentik would always issue a refresh token for the Authorization code and Device code OAuth grants.

Applications that require a refresh token will need their configuration to be updated to include the offline_access scope mapping.

serene valley
#

Update from 2023.10.6 to 2024.4.2 broke OIDC

#

Rolled back to 2023.10.6 for now, otherwise all my services are broken sweat