[web] Validator for passwords

[exalate-issue-sync]

Description

User Stories

• As a user who defines a password in the Web ui, I want instant help to meet the password-policy requirements.

Value

Acceptance Criteria

• if a pw policy is set, users must meet the policy to set passwords
• if a policy is active, it applies to link-password (new and edit password) - won't apply to user accounts
• validation states
  • initial: no requirements are show, the regular password form is visible (submit is inactive);
  • erased: if all input got erased, show all red "X"
  • typed: if 1 or more char are entered, the requirements are shown (submit is inactive)
  • typed: user gets continuously reflected, if the currently typed password meets the requirements (green checks, red crosses) (submit is inactive)
  • valid: submit is active - all requirements are met
• if the policy requires special chars, the ui shows which chars are required (from the backend) see backend ticket: https://jira.owncloud.com/browse/OCIS-3767
• Always show an icon to mask/unmask the entered password (remix icon: eye and eye-off) (regardless if the pw policy is active or not.)
• show a copy icon if the pw was entered
• don't show the copy icon and eye-icon if a saved password exists

Note: for ByCS we have a User-Hint below the password-form (c.f. screenshot) this should be shown above the validation text
Note: this might help: https://github.com/auth0/password-sheriff

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

• Functional requirements
  [ ] functionality described in the user story works
  [ ] acceptance criteria are fulfilled
• Quality
  [ ] code review happened
  [ ] CI is green
  [ ] critical code received unit tests by the developer
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues