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

AuthenticationContext should not be loaded from wildfly-config.xml automatically in deployment

XMLWordPrintable

    • Hide

      1) Add user:

      ./bin/add-user.sh -u user -p pass@123 -r ManagementRealm

      2) Deploy application (see attachment) and access http://127.0.0.1:8080/direct-call-wildfly-config-xml-dep/directCall - it will print user which is username of user set in META-INF/wildfly-config.xml

      Show
      1) Add user: ./bin/add-user.sh -u user -p pass@123 -r ManagementRealm 2) Deploy application (see attachment) and access http://127.0.0.1:8080/direct-call-wildfly-config-xml-dep/directCall - it will print user which is username of user set in META-INF/wildfly-config.xml

      In case when wildfly-config.xml is located in deployment and application server does not have configured default-authentication-context for Elytron subsystem, then AuthenticationContext is automatically parsed from wildfly-config.xml.

      This behavior was changed between EAP 7.1.0.DR11 and EAP 7.1.0.DR12 (try Steps to Reproduce with DR12 as well as DR11).

      In case when default-authentication-context for Elytron subsystem is configured, then AuthenticationContext is correctly loaded from application server.

      If this is intended then it should be reflect in documentation - it currently says that "... they can make use of a configuration file using the parseAuthenticationClientConfiguration(URI) method ...", but in current implementation it is parsed automatically.

      dlofthouse Could you please clarify whether this is intended change or it is an issue?

        1. direct-call-wildfly-config-xml-dep.war
          6 kB

              Unassigned Unassigned
              olukas Ondrej Lukas (Inactive)
              Darran Lofthouse
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: