plucky nest
In the 2023.8.5 version, if you set token validity to 5 minutes as shown in the picture, after 5 minutes, you go to the authenticik site and log in a new token if you are logged in. However, from the 2023.10 version, you ignore this and keep the application session. The test browser was tested with amd64 version of firewall,chrome,edge. The reverse proxy is nginx proxy manager and caddy.
sturdy sky
I have had this problem for a long time and it has already been written about several times, but it is ignored. I set the token's lifetime to 1 day, but it is set to 1 month and cannot be changed.
plucky nest
I have had this problem for a long time and it has already been written about se...
In the 2023.8.5 version, regardless of the cookie expiration date, it moves based on the token settings, but not from the 2023.10 version.
rare berry
Can you try this container image: ghcr.io/goauthentik/dev-server:gh-version-2023.10
plucky nest
Can you try this container image: ghcr.io/goauthentik/dev-server:gh-version-2023...
It's still the same as before.
However, when the authentik session is logged out, the application session is also logged out.
fathom musk
Same for me running on the latest 2023.10.5 😦
rare berry
I’ll have another look later
rare berry
it should be fixed in the latest version of ghcr.io/goauthentik/dev-server:gh-version-2023.10