December 12, 2016 | Written by: Trevor Bodz
Categorized: Community | Compute Services
Share this post:
Heads up: The key you currently use to authenticate against the OpenWhisk API expires on January 12, 2017. From January 12 on, you cannot use this key with OpenWhisk any longer.
What’s happening with OpenWhisk API keys?
OpenWhisk recently changed its authentication methods. Starting December 13, 2016, each key you use to access the OpenWhisk API is bound to exactly one namespace. That means if you want to change your namespace, you also need to switch to another key that belongs to that namespace. The UI will guide you on CLI setup. The REST API will behave accordingly. Visit the Download the OpenWhisk CLI for your new keys.
Important: The namespace (i.e., your e-mail address) will be deprecated as well. This namespace is still accessible through January 11, 2017. If you have any entities in your e-mail address-based namespace, make sure to configure your CLI to point to that namespace explicitly (i.e., wsk property set; namespace firstname.lastname@example.org)—it will not be accessible via the implicit _ namespace any longer. In addition, after January 11, 2017, any entities created under the default namespace (in this case, your “org” name without a space), will be deleted. Please ensure you migrate all entities out of this namespace.
Oh, and one more thing about the namespace
For scripted usages of either the OpenWhisk CLI or API, make sure you have set the namespace you use explicitly. The meaning of the _ namespace will not be the same after the change outlined above. In the future, _ will refer to the namespace bound to the key you’re using instead of the default namespace for your account. So for every key you’re using, the namespace will be different.
Sign up for Bluemix. It’s free!