[Feature] Stay logged in #964
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#964
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'd be nice to have the option to stay logged in.
Especially if you just quickly want to add a task to your todo list but have to log in first + add your 2FA this becomes quite the bothersome task.
Hope that's possible :)
P.s. Not sure if this belongs to api or frontend. Probably both as both would likely need adaption for this to work
The session currently lasts three days. If you access the site within that time, it will be extendend by another three days. So if you use it regularly, you should stay logged in pretty much all the time.
I do see the value of a "stay logged in" checkbox (as usual with other logins) which would extend that. Will look into that but with a low priority.
Awesome, thanks.
I have the tab pinned but add tasks iregularely from different devices so I exceed the 3 day limit pretty much always.
I guess this is done with: vikunja/api#999
I guess if you wanted to have a "remember me" feature, you could store the authentication token in the session storage by default.
When the "remember me" checkbox is ticked, then the token would then be stored in the local storage.
Ofcourse, this would be a frontend issue.
I think there should be a "remember me" function at some point, so this issue can stay open to track that.
@stephen-hill you'll still need to have logic on the api side for "remember me" tokens to get longer lasting tokens. If you store a token for a month that's only valid for three days that's pretty much useless.
Agreed.
API and frontend PRs have just been merged! Please check with the next unstable release (~30 min) of both frontend and API if that solves it.