[jboss-jira] [JBoss JIRA] (WFCORE-3832) [GSS](7.1.z) Support hex encoding in jdbc-realm for elytron
Jan Kalina (JIRA)
issues at jboss.org
Fri May 11 08:14:01 EDT 2018
[ https://issues.jboss.org/browse/WFCORE-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Kalina moved PRODMGT-1881 to WFCORE-3832:
---------------------------------------------
Project: WildFly Core (was: Product Management)
Key: WFCORE-3832 (was: PRODMGT-1881)
Workflow: GIT Pull Request workflow (was: JBoss Platforms RFE Workflow v2)
Component/s: Security
(was: Enterprise Application Platform (EAP))
Affects Version/s: 5.0.0.Alpha7
(was: 7)
> [GSS](7.1.z) Support hex encoding in jdbc-realm for elytron
> -----------------------------------------------------------
>
> Key: WFCORE-3832
> URL: https://issues.jboss.org/browse/WFCORE-3832
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 5.0.0.Alpha7
> Reporter: Jan Kalina
> Assignee: Jimmy Wilson
> 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)
More information about the jboss-jira
mailing list