Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3674

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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 5.0.0.Alpha1
    • None
    • CLI
    • None
    • 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)"

    Description

      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.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. 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)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WFCORE

              People

                jdenise@redhat.com Jean Francois Denise
                jdenise@redhat.com Jean Francois Denise
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: