Home > Blockchain >  Google App Engine: Is there any security concern with giving away datastore urlsafe entity keys in a
Google App Engine: Is there any security concern with giving away datastore urlsafe entity keys in a

Time:11-21

I want to give out anonymous IDs to certain entities in a public token-based API.

Is there any reason I shouldn't be using the urlsafe string of entity keys for that, since they are already anonymized (at least in my case, where I’m not using my own data to construct the key?

Google App Engine and the Datastore are considered safe as long as I'm not handing anyone the key, which I'm not, right?

Thank you.

CodePudding user response:

  1. One of their documentations says ....The urlsafe keyword parameter uses a websafe-base64-encoded serialized reference but it's best to think of it as just an opaque unique string.... I think this is what you're referring to when you say it is anonymized

  2. But a subsequent documentation says ....The string representation of a key looks cryptic, but is not encrypted! It can be converted back to the raw key data, both kind and identifier. If you don't want to expose this data to your users (and allow them to easily guess other entities' keys), then encrypt these strings or use something else....

  • Related