Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: 7.1.0.DR14
Affects Version/s: 7.1.0.DR12
Component/s: Security
Labels:
- cli
- eap71_alpha
- management
- model-controller-client
- remoting
- ssl
- tls

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.1.0.GA
Steps to Reproduce:
Hide

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
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

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?

is cloned by

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

is incorporated by

JBEAP-9193 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta9

is related to

JBEAP-9630 Native management interface ignores SSL/TLS based on Elytron SSL Context when remote protocol is used