Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-9327

It's not possible to set username and password for datasource in elytron-only configuration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.DR14
    • 7.1.0.DR13
    • JCA
    • None
    • User Experience
    • Hide

      remove 

      <extension module="org.jboss.as.security"/>
....
<subsystem xmlns="urn:jboss:domain:security:3.0">

      add elytron-enabled to ExampleDS

      <security>
    <elytron-enabled>true</elytron-enabled>
    <user-name>sa</user-name>
    <password>sa</password>
</security>
      Show
      remove <extension module= "org.jboss.as.security" /> .... <subsystem xmlns= "urn:jboss:domain:security:3.0" > add elytron-enabled to ExampleDS <security> <elytron-enabled> true </elytron-enabled> <user-name> sa </user-name> <password> sa </password> </security>

    Description

      elytron-only = configuration with elytron subsystem and without security subsystem

      It's not possible to set username and password for datasource in elytron-only configuration.

      In elytron-only configuration, attribute elytron-enabled has to be set to true otherwise datasource service fails to start because of dependencies on legacy security services (see JBEAP-8763).

      But when elytron-enabled=true then it's not possible to use username and password (credential-reference doesn't seem to be taken into account - looks like bug with current behavior).

      I expect that users will want to use simple username and password even in elytron-only configuration.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. WFLY-8334 It's not possible to set username and password for datasource in elytron-only configuration

          • 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
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-8763 datasources subsystem should not depend on legacy security subsystem

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: JBEAP

              People

                flaviarnn Flavia Rainone
                msimka@redhat.com Martin Simka
                Martin Simka Martin Simka
                Martin Simka Martin Simka
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: