]
Brian Stansberry commented on WFCORE-4870:
------------------------------------------
PasswordStrengthChecker is an internal API, as is the module that contains it. It could
not stay where it is and be an end user API. I'm not sure where it could go. It would
probably have to be external to WildFly, which is quite a lot.
This involves user configurable behavior so it is a Feature Request.
Improve add-user handling to allow custom dictionary/keyboard
-------------------------------------------------------------
Key: WFCORE-4870
URL:
https://issues.redhat.com/browse/WFCORE-4870
Project: WildFly Core
Issue Type: Enhancement
Reporter: Bartosz Baranowski
Assignee: Bartosz Baranowski
Priority: Minor
As is:
- default Keyboard is properties based setup, it is locked to default EN keyboard layout,
properties file, that it reads are locked in management-domain jar
- default Dictionary is properties based setup, it is locked with few example word
definitions, properties file, that it reads are locked in management-domain jar
- SimplePasswordStrengthChecker - default implementation of password check algorithm.
Sadly with private fields, so it is not extendable( seems like oversight )
- bin/add-user.properties - config file with properties that allow change how
SimplePasswordStrengthChecker or other implementation behaves. It allows to load custom
implementation of PasswordStrengthChecker
Ideally, user should be able to:
- configure layout/dictionary content
- configure implementation of keyboard/dictionary
- extend SimplePasswordStrengthChecker to change keyboard/dictionary, implement more
checks.