Skip to content

SEC-2565: Incorporate Password Storage Scheme spec into stored format #2777

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

Closed
spring-projects-issues opened this issue Apr 18, 2014 · 1 comment
Assignees
Labels
type: jira An issue that was migrated from JIRA
Milestone

Comments

@spring-projects-issues
Copy link

Rob Winch (Migrated from SEC-2565) said:

This would be similar to BCrypt $$$$ This is important so we can upgrade the way users passwords are stored as they authenticate.

NOTE: May be good to support persisting the password differently based upon the user. For example, protect an admin password more than that of average user.

@spring-projects-issues spring-projects-issues added Open type: jira An issue that was migrated from JIRA labels Feb 5, 2016
@rwinch rwinch self-assigned this Oct 25, 2017
@rwinch rwinch added this to the 5.0.0.RC1 milestone Oct 25, 2017
@rwinch
Copy link
Member

rwinch commented Oct 25, 2017

This was taken care of using DelegatingPasswordEncoder in #4666 which maps an id to an instance of PasswordEncoder.

@rwinch rwinch closed this as completed Oct 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: jira An issue that was migrated from JIRA
Projects
None yet
Development

No branches or pull requests

2 participants