Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3832

Support hex encoding in jdbc-realm for elytron

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          is cloned by

          Feature Request - Feature requests from customers and/or users ELY-1582 Support hex encoding in jdbc-realm for elytron

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users WFLY-11073 Support hex encoding in jdbc-realm for elytron

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users HAL-1609 Configure new / enhanced password mappers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement or refactoring of existing functionality WFCORE-3852 Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. WFCORE-3542 Elytron JDBC realm password mapping is not consistent with underlying implementation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              darran.lofthouse@redhat.com Darran Lofthouse
              jkalina@redhat.com Jan Kalina (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: