Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-14335

(7.1.z) Cannot connect to JBoss controller via CLI by passing password in command line if password contains '!' character (for JBoss EAP 7.1 GA in Windows)

XMLWordPrintable

    • Hide

      1. add Management user 'myuser ' with password 'mypass1!'
      2. start JBoss (e.g. in standalone more)
      3. run the following cli:
      jboss-cli.bat -c controller=localhost --user=myuser --password=mypass1! --command=":read-attribute(name=launch-type)"

      Show
      1. add Management user 'myuser ' with password 'mypass1!' 2. start JBoss (e.g. in standalone more) 3. run the following cli: jboss-cli.bat -c controller=localhost --user=myuser --password=mypass1! --command=":read-attribute(name=launch-type)"

      For JBoss EAP 7.1.0.GA in Windows (e.g. Microsoft Windows Server 2016):

      Cannot connect to JBoss controller via CLI by passing password in command line if password contains '!' character. Wrapping password by double quotes does not help.

      For example:

      jboss-cli.bat -c controller=localhost --user=myuser --password=mypass1!
Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: Authentication failed: all available authentication mechanisms failed:
   DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication
Press any key to continue . . .

      In the same time it is possible to connect with such password when cli prompts for it or via management console.

        1. jboss-cli.bat
          3 kB
          Jean Francois Denise

              jdenise@redhat.com Jean Francois Denise
              test00oleksiilv Oleksii V (Inactive)
              Daniel Cihak Daniel Cihak
              Daniel Cihak Daniel Cihak
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: