-
Notifications
You must be signed in to change notification settings - Fork 33
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
Do not store password in localStorage #364
Comments
why? |
It is a bit dangerous to have some critical passwords unencrypted on the browser. |
Is it just for passwords or tokens as well? |
I wish it was the case at least for LDAP passwords. Maybe we should have different policies for each auth plugin? |
We could also store the auth token generated after a succesful LDAP authentication instead of the password in clear? Or would that be still too sensitive? |
We don't have such thing (auth token) with the current LDAP setup. It is using BasicAuth so the username/password are sent as a base64 encrypted Authorization header. If we move to auth0, we would be able to do that. |
This is really important. |
New features * Fix #377, #378: Allow dropping edited resource properties. (#379) * Fix #365: Render a JSON diff for history entries. (#380) * Fix #376: Denote readonly buckets & collections in the sidebar. (#382) * Fix #384: Live-searchable/filterable sidebar entries. (#385) * Hide auth method selector when a single one is configured. Bugfixes * Do not store passwords. Fixes #364 (#386)
Maybe sessionStorage instead?
The text was updated successfully, but these errors were encountered: