[jboss-jira] [JBoss JIRA] (WFCORE-3840) [GSS](7.1.z) Support hex encoding in jdbc-realm for elytron
Jan Kalina (JIRA)
issues at jboss.org
Fri May 11 13:35:01 EDT 2018
Jan Kalina created WFCORE-3840:
----------------------------------
Summary: [GSS](7.1.z) Support hex encoding in jdbc-realm for elytron
Key: WFCORE-3840
URL: https://issues.jboss.org/browse/WFCORE-3840
Project: WildFly Core
Issue Type: Feature Request
Components: Security
Affects Versions: 5.0.0.Alpha7
Reporter: Jan Kalina
Assignee: Jan Kalina
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)
More information about the jboss-jira
mailing list