Loading...

XML

Word

Printable

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?

clones

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

incorporates

JBEAP-7441 Clean up testsuite Elytron registration

is related to

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