-
Feature Request
-
Resolution: Done
-
Major
-
5.0.0.Alpha7
Old database login-module can be configured passing the attribute hashEncoding, for example:
<login-module code="Database" flag="required"> <module-option name="dsJndiName" value="java:jboss/datasources/ExampleDS"/> <module-option name="principalsQuery" value="SELECT password FROM User WHERE username = ?"/> <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM User WHERE username = ?"/> <module-option name="hashAlgorithm" value="SHA-1"/> <module-option name="hashEncoding" value="hex"/> <module-option name="hashCharset" value="UTF-8"/> </login-module>
Currently jdbc-realm in elytron only uses base64 encoding if hash is stored in a text column. This way the migration is more complicated cos the password hash is not valid changing from old security system to elytron.
Think also about the charset attribute.
- is cloned by
-
ELY-1582 Support hex encoding in jdbc-realm for elytron
- Resolved
-
WFLY-11073 Support hex encoding in jdbc-realm for elytron
- Closed
- is related to
-
HAL-1609 Configure new / enhanced password mappers
- Resolved
-
WFCORE-3852 Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker
- Open
- relates to
-
WFCORE-3542 Elytron JDBC realm password mapping is not consistent with underlying implementation
- Resolved