Collaborator 13.2 and 13.4 cannot login in the command line if the password contains a double-quote

Question

Any time the&nbsp;password contains a double-quote, the login command below raises an exception.&nbsp;Example: if the password is 123"456, then the login command must be:ccollab.exe login&nbsp;https://collabserver.io&nbsp;Matei&nbsp; "123""456"&nbsp;The Collaborator server throws an exception:Trying to login with new configurationjava.net.SocketException: Network is unreachable: connectat java.net.DualStackPlainSocketImpl.connect0(Native Method)&nbsp;ERROR: Executing command `ccollab login`:java.io.IOException: Network is unreachable: connectcom.smartbear.collaborator.client.exceptions.CollabClientException: java.io.IOException: Network is unreachable: connect&nbsp;The correct answer from the server would have been:&nbsp;Connecting to Collaborator Enterprise v13.4.13401 Server https://collabserver.io&nbsp;Collaborator Enterprise client credentials invalid. Please supply a valid password.&nbsp;This situation was not present in version 12.4, the double-quote was accepted in the password!

joseph_michaud · Answer

Try surrounding the password with *single* quotes.

mateiacd · Answer

And what if the password contains a single-quote and a double-quote, like this: 123"4'56 ?

joseph_michaud · Answer

This isn't a Collaborator problem . . . it is a Windows CMD shell problem.&nbsp; You will have a problem with other characters as well (like caret ^ and ampersand &amp; and percent %).&nbsp; There doesn't seem to be a simple clean way to do this.
&nbsp;

mateiacd · Answer

A command line with arguments is not necessarily executed in a cmd.exe window where escaping restrictions apply for &amp; % ^ " etc.I can execute the ccollab.exe login command with Win32 API functions or with C# process launching functions, or with Python or Java.In these languages, no escaping restrictions are necessary, except those required by the language and the use of two double-quotes for escaping a single double-quote inside an argument.Because the arguments are always (normally?) passed to executables surrounded by double-quotes, aren't they?What are the new rules of passing arguments to the ccollab.exe login command in Collaborator since 13.2?I think it is Collaborator's responsibility to define the rules of passing arguments to its commands.

mateiacd · Answer

At our company we have no Collaborator 12.4 server anymore to test, we have upgraded to 13.4.13104, but I can guarantee that&nbsp;the command below worked perfectly fine in 12.4:ccollab.exe login&nbsp;https://collabserver.io&nbsp;Matei&nbsp; "123""456"And now starting with 13.2 the command raises a weird exception.

Forum Discussion

Collaborator 13.2 and 13.4 cannot login in the command line if the password contains a double-quote

Related Content

Property transfer version 5.7.2 not removing double quotes.

Double quotes added to variables

Password Variable not passing the password

JDBC Connection String, Issue with the password

New Collaborator install fails to load page.

Recent Discussions

I don't see an option to generate login ticket for collaborator .

Users logged out of web interface too soon

Collaborator insists on downloading .docx files in a review.

Code Collaborator Redirects to Init/Login Page Endlessly

Code Collaborator won't Start