We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When setting password min and max length through the console UI, Identity Server does not allow values above 30 for the maximum length.
But when configuring max password length through the validation API, Identity Server allows to set values above 30.
Try to update the max password length through the console app. Max value is set as 30.
Use below CURL to update the max password length through API. Password max length is successfully updated to 32.
curl --location --request PUT 'https://localhost:9443/api/server/v1/validation-rules/password' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --header 'Authorization: Basic YWRtaW46YWRtaW4=' \ --data-raw '{ "rules": [ { "validator": "LengthValidator", "properties": [ { "key": "min.length", "value": "8" }, { "key": "max.length", "value": "32" } ] } ] }'
Both flows should be consistent.
Product Version: IS 7.0.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the issue:
When setting password min and max length through the console UI, Identity Server does not allow values above 30 for the maximum length.
But when configuring max password length through the validation API, Identity Server allows to set values above 30.
How to reproduce:
Try to update the max password length through the console app. Max value is set as 30.
Use below CURL to update the max password length through API. Password max length is successfully updated to 32.
Expected behaviour :
Both flows should be consistent.
Environment information :
Product Version: IS 7.0.0
The text was updated successfully, but these errors were encountered: