[jboss-jira] [JBoss JIRA] (WFLY-2950) jboss-cli using https-remoting: command not executed if certificate is unrecognised

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980174#comment-12980174 ] 

RH Bugzilla Integration commented on WFLY-2950:
-----------------------------------------------

mark yarborough <myarboro at redhat.com> changed the Status of [bug 1026418|https://bugzilla.redhat.com/show_bug.cgi?id=1026418] from VERIFIED to CLOSED

> jboss-cli using https-remoting: command not executed if certificate is unrecognised
> -----------------------------------------------------------------------------------
>
>                 Key: WFLY-2950
>                 URL: https://issues.jboss.org/browse/WFLY-2950
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: CLI, Domain Management
>    Affects Versions: 8.0.0.Final
>         Environment: Windows 7 Pro
>            Reporter: Darren Jones
>            Assignee: Darran Lofthouse
>              Labels: cli, shutdown
>             Fix For: 8.1.0.CR1, 8.1.0.Final
>
>
> When using the https management interface from jboss-cli, commands passed with a command line option (such as --command=:shutdown) are not executed if the server certificate is unrecognised - even if accepting the certificate [T]emporarily or [P]ermenantly.
> It appears to be due to the CommandContextImpl.handleSSLFailure() method, which calls error("Unable to connect..."). The error() method sets the exitCode to 1. So, when CliLauncher.processCommands() subsequently runs, it sees that the cmdCtx.exitCode is 1 and ignores any commands.
> I guess the handleSSLFailure needs to reset the exitCode to 0 if the user chooses [T] or [P].



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)