[
https://issues.jboss.org/browse/ELY-1582?page=com.atlassian.jira.plugin.s...
]
Jan Kalina moved WFCORE-3840 to ELY-1582:
-----------------------------------------
Project: WildFly Elytron (was: WildFly Core)
Key: ELY-1582 (was: WFCORE-3840)
Component/s: Realms
(was: Security)
Affects Version/s: 1.3.2.Final
(was: 5.0.0.Alpha7)
[GSS](7.1.z) Support hex encoding in jdbc-realm for elytron
-----------------------------------------------------------
Key: ELY-1582
URL:
https://issues.jboss.org/browse/ELY-1582
Project: WildFly Elytron
Issue Type: Feature Request
Components: Realms
Affects Versions: 1.3.2.Final
Reporter: Jan Kalina
Assignee: Jan Kalina
Labels: elytron
Old database login-module can be configured passing the attribute {{hashEncoding}}, for
example:
{code:xml}
<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>
{code}
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.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)