We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
it seems the token format is incorrect, when using the CLI to create the edgekv_tokens.js file.
edgekv_tokens.js
akamai edgekv create token my-new-token --save_path=mypath --overwrite --staging=allow --production=allow --ewids=1234 --namespace=myspace+r var edgekv_access_tokens = { "myspace" : { "name": "my-new-token", "reference" : "xxxxxxxxxxxxxxxxxxxxxxxx" } } export { edgekv_access_tokens };
The field value myspace will cause the EdgeWorker to fail, with MISSING ACCESS TOKEN. No EdgeKV Access Token defined for namespace "myspace"
myspace
MISSING ACCESS TOKEN. No EdgeKV Access Token defined for namespace "myspace"
Expected field value is namespace-myspace, as per the documentation in https://techdocs.akamai.com/edgekv/docs/generate-and-retrieve-edgekv-access-tokens#edgeworker-id where the parent key names must start with namespace-
namespace-myspace
# akamai edgekv --version 1.9.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
it seems the token format is incorrect, when using the CLI to create the
edgekv_tokens.js
file.The field value
myspace
will cause the EdgeWorker to fail, withMISSING ACCESS TOKEN. No EdgeKV Access Token defined for namespace "myspace"
Expected field value is
namespace-myspace
, as per the documentation in https://techdocs.akamai.com/edgekv/docs/generate-and-retrieve-edgekv-access-tokens#edgeworker-id where the parent key names must start with namespace-The text was updated successfully, but these errors were encountered: