This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Remember me #613
Comments
@sn00pster Thanks for your request. |
Portainer is great but why do I have to login each time I open a new tab? I'm trying to use direct links like this (makes it very easy for non-docker users to work with a container): I verified my docker (Ubuntu16) and browser are using the correct time. Even restarted the portainer container. So I don't think it's related to #398. How can I diagnose the problem, which cookie contains authentication (JWT?) and why isn't it a browser-wide, long-lived cookie? |
Okay, but imo that's extremely unfriendly UX. People like working with multiple tabs open and hate having to re-login. Even non-technical users use right-click Open Link in New Tab. Instead consider making it an HttpOnly or "secure" cookie and require https. Running portainer over http is a much more serious security issue than cross-tab cookies. Thanks for keeping this open, maybe more users will +1 and you'll reconsider. |
Yes, opening up new tabs for different pages is great for compare-and-contrast activities, and is such a major part of my workflows that I'm currently stuck using an older version of Portainer. I know Portainer's UI is based on a single-page design, but I'm hoping this gets fixed soon so I can start following the mainline again. |
@ncresswell why are cookies required? Can't you store the token in |
@nathantreid Token was originally stored in the Now, with the more recent feedback about the usage of Portainer, it seems that a lot of people actually want to use multi-tabs (which I think is because of a UX problem with Portainer but that's another discussion), so we can switch the storage from Note that I'll open another issue for that, as it's not related to the remember-me feature request asked in this issue. Edit: done, tracked in #910 |
I think this could easily be solved by saving the Token in either the SessionStorage or the LocalStorage. Depending on whether remember me is on or off. |
Until this is implemented, users will have the ability to set a longer session timeout of 8hrs via #3846 |
Setting Session lifetime to |
Any updates on this? |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
A remember me checkbox on the login would be nice to save logging in every time and take you directly to the dashboard.
The text was updated successfully, but these errors were encountered: