CLI password issue with JBoss 6.1.1 EAP

[mdzmura]

I am trying to automate some stuff with the CLI but am having an issue with putting a password on the CLI command line.

If I try to include the password in the command line:

    --password=<password>

OR

    --password="<password>"

then the connect attempt fails with the "tried all authentication methods" error.

However, if I OMIT the --password on the command line, then the CLI prompts me for the password - I type in the same password and it consistently authenticates with no issues.

Let me note that the password in use is pretty funky, 16 characters with mixed case, numbers, and a bunch of punctuation.

The operations folks make the passwords using rules, so I'll have to have a good reason to change it.

Any ideas on why putting the password on the CLI command line does not work?

Thanks,

Mark

[jason.marley]

I've had issues before where my --password was not following the proper syntax parameters and it would fail, but once I followed it worked well. My guess is that some of the characters used and being interpreted not as a string, but additional options.

try:

--password='<password>'

with single quotes usually will not allow anything in-between them to be executed.

Jason

[marcelomrwin]

Man, look if in your password exists some characters like '@' or '$'. I've had the same issue before because my password has '$'. I resolved my problem using double $ to pass the password. For example, if you password is T$ST then you must pass T$$ST as parameter to your connection. I dont know why but worked for me. Now my connection works even if no quotes. --password T$$ST works like a charm.

[mdzmura]

Jason - Thanks, but no cigar.  I tried it with single quotes and the result was the same.

Marcelo -  the punctuation characters used in the password are   % # ? !                       I will experiment with doubling them.

I neglected to mention in my first post that the client platform is Windows 7.

Thanks,

Mark

[mdzmura]

I tried every combo of doubling the punctuation chars, still was not able to authenticate.

I really need to find a solution to this, since Operations got back to me and said any password they give me will be of the same form, with punctuation... :-(

-Mark