Issue with escaping passwords when using Service Mode REST API record-add

[lennartki]

When creating records through Service Mode REST API i'm having a hard time escaping special characters. Are there any other options available like password_base64 argument option which would simplify storing passwords with special characters?

[amangalampalli-ks]

Hi @lennartki,

For most special characters, you can use single quotes in the command string:

{
  "command": "record-add -t \"My Account\" -rt login login=admin password='Pass123!@#$%^&*()'"
}

This works well for !@#$%^&*() and similar characters.

Could you share what specific special characters are causing issues? This will help us provide a more targeted solution.

[lennartki]

Hi @amangalampalli-ks ,

Thank you very much for your helpful response and advice about using single quotes to handle special characters!

I have to admit, I’m not very handy with computers or complex command-line escaping, so I’m struggling a bit with the current approach. For example, my password is:

fjhdfh\"%'sdkhf"dskjhfd

As you can see, it contains a mix of double quotes, single quotes, backslashes, and other special characters, and it’s quite tricky for me to properly escape everything to make it work with the service mode REST API.

Would it be possible to consider making this process easier or more user-friendly for people like me who aren’t very technical? Perhaps an option to provide passwords without needing complex escaping, or supporting base64-encoded passwords, could be really helpful.

Thanks so much for your time and all the work on Keeper Commander — I really appreciate it!