Graph passwords with some special characters are not escaped

[alyssadai]

Is there an existing issue for this?

• I have searched the existing issues
• Related to [TBD] Passwords with $ in them break setup #59

Expected Behavior

My NB_GRAPH_ADMIN_PASSWORD.txt contains:

pXLUj\$rb_rLcH

I would expect this password to be set successfully, exactly as defined, during GraphDB server setup, and for queries from the node API to succeed (using this password behind the hood) without authorization errors.

Current Behavior

• There is an error from GraphDB regarding escape characters during setup, during the step where the admin password should be changed:

{"message":"JSON parse error: Unrecognized character escape '$' (code 36); nested exception is Unrecognized character escape '$'
...

• this is because even though the password string is passed as-written, it results in the payload being invalid JSON, due to the presence of an invalid escape \$, e.g.:

  { "password": "pXLUj\$rb_rLcH" }

  similarly, to be safe, quotes, slashes, and unexpected control characters (tab, newline, etc.) should be explicitly escaped in the value to ensure proper JSON parsing

• The node API returns a 401 Unauthorized error when a query is submitted

• NOTE: this appears to only be an issue for JSON payloads in curl requests - credentials provided using the -u flag are parsed as expected, e.g.
  

  recipes/scripts/graphdb_setup.sh

  Line 182 in ef1dcc5

  curl -X PUT -u "admin:${ADMIN_PASS}" http://localhost:${NB_GRAPH_PORT}/${NB_GRAPH_DB} --data-binary "@data-config.ttl" -H "Content-Type: application/x-turtle"

Error message

No response

Environment

• OS:
• Python/Node version:

How to reproduce

No response

Anything else?

No response

[neurobagel-bot]

🚀 Issue was released in v0.4.2 🚀