Invalid JWT should redirect frontend to login page #1927

New Issue

distrobyte · 2022-07-07T10:15:22Z

distrobyte commented

2022-07-07 10:15:22 +00:00

When the Vikunja container is recreated, all the tokens become expired. A user trying to log in after this happens is not directed to the login page, instead a small error is displayed in the bottom corner which says that the JWT is expired.

A potential solution to this would be to redirect to the login page on expired JWT, unsure how feasible this will be as the login page and the "home" page are at the same URL.

When the Vikunja container is recreated, all the tokens become expired. A user trying to log in after this happens is not directed to the login page, instead a small error is displayed in the bottom corner which says that the JWT is expired. A potential solution to this would be to redirect to the login page on expired JWT, unsure how feasible this will be as the login page and the "home" page are at the same URL.

konrad added the

kind/feature

label 2022-07-07 13:06:06 +00:00

konrad commented

2022-07-07 13:08:26 +00:00

You'll want to set a jwt secret to avoid all sessions getting invalidated when you restart the container.

In the next release (already in unstable) the behaviour was changed to do exactly what you're describing: When the user visits the page with an expired token the login page is displayed instead of an error.

You'll want to set a [jwt secret](https://vikunja.io/docs/config-options/#jwtsecret) to avoid all sessions getting invalidated when you restart the container. In the next release (already in unstable) the behaviour was changed to do exactly what you're describing: When the user visits the page with an expired token the login page is displayed instead of an error.

konrad closed this issue

2022-07-07 13:08:26 +00:00

konrad referenced this issue from a commit

2024-02-07 14:00:34 +00:00

feat: description script setup (#1927)

Sign in to join this conversation.