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

Configured set-protocol in Elytron Client configuration file is not used

    XMLWordPrintable

Details

    Description

      When some configuration in Elytron Client configuration file uses set-protocol then value of this element is not used for outgoing connection. Elements set-host and set-port are used correctly.

      Following authentication configuration part of wildfly-config.xml should use URL remote+http://localhost:9990 for outgoing connection, but protocol remote+http from set-protocol is not used:

      <authentication-configurations>
    <configuration name="auth-config">
        <set-user-name name="user"/>
        <set-protocol name="remote+http"/>
        <set-host name="localhost"/>
        <set-port number="9990"/>
        <credentials>
            <clear-password password="password"/>
        </credentials>
    </configuration>
</authentication-configurations>

      We request blocker because this issue blocks feature for RFE EAP7-567. Due to issue incorrect protocol can be unexpectedly used for outgoing connection, e.g. http can be used instead of https.

      This issue is blocker for GA, not for testing.

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10544 Attribute protocol in authentication-configuration of Elytron subsystem is not used

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ELY-1100 Configured set-protocol in Elytron Client configuration file is not used

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-10845 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta23

          • 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.
          • Verified

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-11280 Upgrade remoting to 5.0.0.Beta25

          • 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.
          • Verified

          Activity

            People

              thofman Tomas Hofman
              olukas Ondrej Lukas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: