What happens to an existing API key in the Knox Configure console when I generate a new one?

Knox Configure technical FAQs

If a trial license expires before the customer changes it to commercial, how can customer apply a commercial license?
I try to upgrade an application already installed in device using KC. While a new version of application is being installed in device after a new profile with a new app is assigned, an error occurs. I don’t know what’s wrong.
Why is the WKC client app not automatically updating my wearable device when a push update is sent?
How do I fix “signing failed” error cases?
How long does it take the app to change status to “Ready to deploy” after uploading to the Knox Configure console?
Does a wearable device need a network connection to receive push updates?
How do I set up my Knox Configure account for the first time?
Why do I get an error message when I try to add an admin to my Knox Configure tenant?
How do I find a Knox Configure Customer ID?
What is the difference between the Knox Customer ID and the internal customer reference?

Article ID: 115013540848
April 26, 2018 10:24

When a new API key generates, the previous API key is invalidated. The services configured with the previous API key will not work until they are updated with the new API key.

Was this article helpful?

Sorry about that

Why wasn't this helpful? (check all that apply)

Couldn't find what I was looking for

Information confusing or unclear

Instructions didn't work

Comments

Great!

Thanks for taking the time to give us some feedback.

Additional Support

Enroll or sign in to submit support tickets

Looking for other product help?

ARTICLES IN THIS SECTION

What happens to an existing API key in the Knox Configure console when I generate a new one?

Sorry about that

Great!

Additional Support

Looking for other product help?

Technical support

Consumer support