Skip to content
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

Add documentation for support of score-based password verification[DOC] #4088

Closed
4 tasks
cwillum opened this issue May 16, 2023 · 2 comments · Fixed by #4267
Closed
4 tasks

Add documentation for support of score-based password verification[DOC] #4088

cwillum opened this issue May 16, 2023 · 2 comments · Fixed by #4267
Assignees
Labels
1 - Backlog Issue: The issue is unassigned or assigned but not started security

Comments

@cwillum
Copy link
Contributor

cwillum commented May 16, 2023

What do you want to do?
Add documentation for support of score-based password verification using the zxcvbn library.

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request.
Two new settings have been added to support this feature:

  • plugins.security.restapi.password_min_length
  • plugins.security.restapi.password_score_based_validation_strength

What other resources are available?
This issue is based on Security PR #2557.

@cwillum cwillum added 1 - Backlog Issue: The issue is unassigned or assigned but not started security labels May 16, 2023
@cwillum cwillum self-assigned this May 16, 2023
@cwillum cwillum removed the untriaged label May 16, 2023
@RyanL1997
Copy link

Hi @cwillum, thank you for follow up on this, and here is a brief summary of some of the specific details of the password validation:

  1. If the user enable the password strength feature, it will only apply on the non-reserved internal user, which are the users created by internal user api. The reserved users will not apply these rules.
  2. The minimum password length required under these validation rules are 8.
  3. The possible values the strength of the valid password:
    fair - very guessable password: protection from throttled online attacks
    good - somewhat guessable password: protection from unthrottled online attacks
    strong - safely unguessable password: moderate protection from offline slow-hash scenario
    very_strong - very unguessable password: strong protection from offline slow-hash scenario
  4. By default the plugin always checks strength of the password and its minimal length together with the regular expression if its set.

@cwillum
Copy link
Contributor Author

cwillum commented Jun 7, 2023

@RyanL1997 Many thanks for summarizing the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog Issue: The issue is unassigned or assigned but not started security
Projects
None yet
2 participants