...
- ID: The ID of the user API key. This is the first 32 characters of the full user API key. The ID does not contain the secret of the API key.
- NAME: The name of the API key.
- STATE: Indicates whether the API key is currently Enabled, Disabled, or Expired. An enabled API key is available for use while an expired key is no longer valid. You can enable and disable a valid user API key, but you cannot enable or disable an expired one. Fourteen (14) days prior to expiration of your user API key, BloxOne will notify you in-app and via email on a daily basis. You can create a new API key to replace the expiring one, and then delete the old one when it expires.
- EXPIRES AT: The timestamp when the API key will expire or has expired.
- LAST USED AT: The timestamp when the API key was last used in an API operation. For troubleshooting purposes, this gives you an idea when the API key was last used in case of suspicious activities.
- CREATED AT: The timestamp when the API key was first created.
- UPDATED AT: The timestamp when the API key was last updated.
- TYPE: The type of API key. This can be one of the following:
- Interactive: Interactive API keys are user API keys created by the signed-in users themselves.
Legacy: Legacy API keys are user API keys automatically generated for the signed-in users in previous BloxOne releases.
| Note | ||
|---|---|---|
| ||
| Infoblox will deprecate legacy keys in the near future. It is recommended that you replace your legacy key with interactive user API keys. For information about how to migrate legacy API keys to service API keys, see Migrating Legacy API Keys to Service API Keys. |
- CREATED BY: The user who created this API key.
...