Encode keys in URLs with base64url raw

[tock-ibm]

Signed-off-by: Yoav Tock [email protected]

[liran-funaro]

My only note is that the issue that this PR solves can appear for every string that is passed via a rest API. This includes the keys, but also the DB name and the user ID.
I suggest modifying the API to support base64 encoding for these fields.
Otherwise, a user might be able to create a field (via post request) that it cannot access.
Alternatively, we can add a separate rest API (e.g., with a prefix /base64/...) that all names are referred to using a base64 encoding (in parallel to the plain text API).

[tock-ibm]

My only note is that the issue that this PR solves can appear for every string that is passed via a rest API. This includes the keys, but also the DB name and the user ID. I suggest modifying the API to support base64 encoding for these fields. Otherwise, a user might be able to create a field (via post request) that it cannot access. Alternatively, we can add a separate rest API (e.g., with a prefix /base64/...) that all names are referred to using a base64 encoding (in parallel to the plain text API).

I agree that this is a potential problem to every field, and this is indicated in the issue. In other field we can enforce naming conventions that are URL and file friendly, and rejecting TXs that try and create usernames and database names that violate these restrictions, e.g. #49 #483 #482