that the password input needs to be it's own ui-component and that some additional discovery and design work needs to be done.
Acceptance criteria
Decide on design direction
Coordinate with DDI platform team to get this password validation incorporated into KeyCloak sign in shared service
Outline the default validator(s) that we should include in the component e.g. Will we have a custom solution that surfaces the password rules and gives feedback to the user in real time?
At least 12 characters.
A mixture of both uppercase and lowercase letters.
A mixture of letters and numbers.
Inclusion of at least one special character, e.g., ! @ # ? ]
Design validation messaging that corresponds to the validator(s) that we define
Create documentation in Figma for password input (pattern?)
Spark450
commented
5 hours ago
Background
Through issue https://goa-dio.atlassian.net/browse/DDIDS-725
that the password input needs to be it's own ui-component and that some additional discovery and design work needs to be done.
Acceptance criteria
Decide on design direction
Coordinate with DDI platform team to get this password validation incorporated into KeyCloak sign in shared service
Outline the default validator(s) that we should include in the component e.g. Will we have a custom solution that surfaces the password rules and gives feedback to the user in real time?
At least 12 characters.
A mixture of both uppercase and lowercase letters.
A mixture of letters and numbers.
Inclusion of at least one special character, e.g., ! @ # ? ]
Design validation messaging that corresponds to the validator(s) that we define
Create documentation in Figma for password input (pattern?)