End-of-Life (EoL)
Description
Generate API keys on a WF-500 appliance that you will use on an external system to submit samples to the appliance, query reports, or retrieve samples and Packet Captures (PCAPS) from the appliance.
Syntax
create {
wildfire {
api-key {
key <value>;
name <value>;
{
{
{
Options
+ key — Create an API key by manually entering a key value. The value must be 64 alpha characters (a-z) or numbers (0-9). If you do not specify the key option, the appliance generates a key automatically.
+ name — Optionally enter a name for the API key. An API key name is simply used to label the keys to make it easier to identify keys assigned for specific uses and has no impact on the functionality of the key.
Sample Output
The following output shows that the appliance has three API keys and one key is named my-api-key.
admin@WF-500> show wildfire api-keys all
+--------+----------------+---------------------+---------------------+
| Apikey | Name | Status | Create Time | Last Used Time |
+---------------------------------------------------------------------
+-----------+------------+----------------------+---------------------+
| <API KEY> | my-api-key | Enabled | 2014-06-24 16:38:50 |
| <API KEY> | test-api-key | Enabled | 2014-06-25 09:05:30 | 2014-06-26 14:49:35 |
| <API KEY> | test2-api-key | Enabled | 2014-08-04 17:00:42 |
+----------------------------------------------------------
Required Privilege Level
superuser, deviceadmin

Recommended For You