Bug 1238609 - Support for true non-interactive mode
Summary: Support for true non-interactive mode
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI
Version: 6.4.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Bartek Spyrko-Smietanko
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-02 09:33 UTC by Libor Zoubek
Modified: 2015-11-02 00:44 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-10 12:38:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1238263 0 unspecified CLOSED [QA] (6.4.z) jboss-cli client prints "Accept certificate? [N]o, [T]emporarily, [P]ermenantly" indefinitely 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker WFCORE-869 0 Major Resolved command line option to turn off CLI security prompts in non-interactive mode 2017-06-16 17:20:07 UTC

Internal Links: 1238263

Description Libor Zoubek 2015-07-02 09:33:48 UTC
Description of problem:
My server's management interfaces are secured with SSL certificate and I am trying to run

jboss-cli --connect --commands ":whoami" 

In case I did not permanently accept the certificate before nor configured it in jboss-cli.xml, process is blocked until I provide some input.

Version-Release number of selected component (if applicable):
all 6.x.x


Steps to Reproduce:
1. Secure native interface with SSL (and/or client certificate)
2. make sure $HOME/.jboss-cli.truststore does not exist
3. execute jboss-cli --connect --commands ":whoami"

Actual results:
In case I did not permanently accept the certificate before nor configured it in jboss-cli.xml, process is blocked until I provide some input.

Expected results:
I need to be able to run CLI with some special flag, so it terminates immediately in case client does not (yet) trust the server certificate. The use case is in RHQ Agent plugin, which can execute jboss-cli. If server's native interface is secured, our plugin get's blocked, because jboss-cli is waiting for input. We need to fix it, so the user at least knows, he has to properly configure jboss-cli.xml.

Additional info:

Comment 1 baranowb 2015-07-07 10:16:07 UTC
Flags + NACK. This seems like RFE.

Comment 2 Libor Zoubek 2015-07-07 10:32:40 UTC
I don't see it as RFE as this page https://developer.jboss.org/wiki/CLINon-interactiveMode describes how to run in non-interactive mode. This is broken by the fact, that server is secured and it's cert not trusted.

Comment 3 Bartek Spyrko-Smietanko 2015-08-06 11:00:18 UTC
Upstream issue: https://issues.jboss.org/browse/WFCORE-869
Upstream PR: https://github.com/wildfly/wildfly-core/pull/944

Comment 4 Darran Lofthouse 2015-08-06 11:10:53 UTC
+1 on this being classed as an RFE, the existing behaviour covers a set of valid use cases.

Changing the existing behaviour is not acceptable.

Comment 5 Bartek Spyrko-Smietanko 2015-08-10 12:38:40 UTC
Closing - the upstream RFE is https://issues.jboss.org/browse/WFCORE-869

Comment 6 JBoss JIRA Server 2015-09-14 13:02:39 UTC
Alexey Loubyansky <alex> updated the status of jira WFCORE-869 to Resolved

Comment 7 JBoss JIRA Server 2015-09-15 14:45:44 UTC
Alexey Loubyansky <alex> updated the status of jira WFCORE-869 to Reopened


Note You need to log in before you can comment on or make changes to this bug.