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

Native management interface does not work with SSL/TLS based on Elytron SSL Context

    XMLWordPrintable

Details

    • Hide
      1. Add socket-binding-group: /socket-binding-group=standard-sockets/socket-binding=native:add(port=9999)
      2. Using the socket-binding-group, follow [1] or [2] to set management native-interface (instead of http-interface) backed by SSL Context from Elytron
      3. Run ./bin/jboss-cli.sh --controller=remote+https://localhost:9999 -c or ./bin/jboss-cli.sh --controller=https-remoting://localhost:9999 -c
      Show
      Add socket-binding-group : /socket-binding-group=standard-sockets/socket-binding=native:add(port=9999) Using the socket-binding-group , follow [1] or [2] to set management native-interface (instead of http-interface ) backed by SSL Context from Elytron Run ./bin/jboss-cli.sh --controller=remote+ https://localhost:9999 -c or ./bin/jboss-cli.sh --controller=https-remoting://localhost:9999 -c

    Description

      Following [1,2] to set management native-interface backed by SSL Context from Elytron, jboss-cli connection results in:

      Failed to connect to the controller: Unable to negotiate SSL connection with controller at localhost:9999

      Are there any configuration steps that needs to be performed for this configuration to work?

      [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildFlyElytronSecurity-EnableOnewaySSL%2FTLSfortheManagementInterfacesUsingtheElytronSubsystem
      [2] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildFlyElytronSecurity-EnableTwowaySSL%2FTLSfortheManagementInterfacesusingtheElytronSubsystem

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2333 Native management interface does not work with SSL/TLS based on Elytron SSL Context

          • 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-9193 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta9

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9630 Native management interface ignores SSL/TLS based on Elytron SSL Context when remote protocol is 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

          Activity

            People

              darran.lofthouse@redhat.com Darran Lofthouse
              okotek@redhat.com Ondrej Kotek
              Ondrej Kotek Ondrej Kotek
              Ondrej Kotek Ondrej Kotek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: