[jboss-jira] [JBoss JIRA] (WFLY-4667) CLI authentication fails when --command is used
Marek Kopecký (JIRA)
issues at jboss.org
Mon Jun 8 06:46:02 EDT 2015
[ https://issues.jboss.org/browse/WFLY-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13075305#comment-13075305 ]
Marek Kopecký commented on WFLY-4667:
-------------------------------------
Steps from description in this jira works in EAP 6, but adding "--username" and "--password" in non-interactive mode makes sense.
> CLI authentication fails when --command is used
> -----------------------------------------------
>
> Key: WFLY-4667
> URL: https://issues.jboss.org/browse/WFLY-4667
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.Alpha1
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
>
> Description of problem:
> CLI is unable to use --command argument, when authentication is used
> How reproducible:
> Always
> Steps to Reproduce:
> 1. cd bin
> 2. ./standalone.sh &
> ./jboss-cli.sh -c command=/core-service=management/security-realm=ApplicationRealm/authentication=local:remove
> ./jboss-cli.sh -c command=/core-service=management/security-realm=ManagementRealm/authentication=local:remove
> ./jboss-cli.sh -c command=:shutdown
> 3. cd ..
> 4. echo "bob=81ce18184f7b1095a367d5fae624ac15" >> standalone/configuration/mgmt-users.properties
> 5. ./bin/standalone.sh &
> 6. ./bin/jboss-cli.sh -c --command=':shutdown'
> Actual results:
> Authenticating against security realm: ManagementRealm
> Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: Authentication failed: all available authentication mechanisms failed:
> DIGEST-MD5: java.lang.NullPointerException
> Expected results:
> manually set login information (bob, admin123@) and ":shutdown" command will be executed
> Additional info:
> These commands are working correctly:
> 6. ./bin/jboss-cli.sh -c
> 7. bob
> admin123@
> :shutdown
> exit
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list