Description of problem: Command passed as arguments to CLI is not executed once I choose to accept the SSL certificate only temporarily. Version-Release number of selected component (if applicable): EAP 6.2.0.ER7 How reproducible: Always Steps to Reproduce: 0. Navigate to JBOSS_HOME/bin. 1. Create SSL certificate like: keytool -genkeypair -alias alias -keyalg RSA -keystore ssl-test.keystore -storepass password --dname "CN=jboss,OU=Engineering,O=redhat.com,L=Brno,C=CZ" 2. Start standalone server. 3. Secure ManagementRealm with SSL: ./jboss-cli.sh -c command="/core-service=management/security-realm=ManagementRealm/server-identity=ssl:add(keystore-path=ssl-test.keystore,keystore-password="password")" 4. Restart server 5. Stop the server using non-interactive CLI mode, accept the certificate only temporarily. ./jboss-cli.sh -c shutdown Accept certificate? [N]o, [T]emporarily, [P]ermenantly : T Actual results: CLI command is not executed. Expected results: CLI command is executed. Additional info: Even if I accept the certificate permanently the first command is not executed (step 5). After accepting the certificate, one must call the command again to shutdown the server.
Assigning to me as I am currently working on improving the certificate acceptance logic upstream.
Darran Lofthouse <darran.lofthouse> made a comment on jira WFLY-2538 Additional testing and this does not seem to be restricted to the certificate acceptance prompt, if the user is required to authenticate and provide a username and password the same behaviour is observed.
Darran Lofthouse <darran.lofthouse> made a comment on jira WFLY-2538 -Additional testing and this does not seem to be restricted to the certificate acceptance prompt, if the user is required to authenticate and provide a username and password the same behaviour is observed.- Ignore this comment, further testing does appear to be specific to certificate acceptance.
Darran Lofthouse <darran.lofthouse> updated the status of jira WFLY-2538 to Coding In Progress
Adding devel_ack as the upstream issue is resolved so should be a trivial backport.
Verified on EAP 6.3.0.DR6.