Cisco Splunk Credentials
Cisco Splunk Credentials provide secure authentication for workflows interacting with Cisco Splunk management REST APIs and optional HTTP Event Collector endpoints. To enable Workflows to authenticate API requests, create a Cisco Splunk account key using the authentication method supported by your Splunk deployment.
Use Cisco Splunk Credentials account keys with Cisco Splunk workflow activities and Cisco Splunk Endpoint targets.
Prerequisites
Before starting the account key setup procedure, obtain one of the following credential sets:
-
An API token for token-based authentication.
-
A username and password for session login or basic authentication.
-
An HEC token if workflows will send events through HTTP Event Collector.
Adding Cisco Splunk Credentials
Complete the following steps to create a new Cisco Splunk Credentials account key:
-
From the left navigation menu, click Automation > Account Keys.
-
Click New Account Key.
-
From the Account Key Type drop-down list, choose Cisco Splunk Credentials.
-
Enter a unique display name for the account key in the Display Name field and a brief description in the Description field.
-
In the Authentication area, choose the Authentication Type: API Token, Session Login, or Basic Auth.
-
Enter the credential fields required for the selected authentication type.
-
In the Secondary Endpoints area, enter HEC Token only if workflows will send events through HTTP Event Collector.
-
Click Save to save the credential.
Credential Fields
| Field | Required | Secret | Description |
|
Authentication Type |
Yes |
No |
Selects API Token, Session Login, or Basic Auth. |
|
API Token |
Required when Authentication Type is API Token. |
Yes |
Token used to authenticate Cisco Splunk management REST API requests. |
|
Username |
Required when Authentication Type is Session Login or Basic Auth. |
No |
Username used for Splunk session login or basic authentication. |
|
Password |
Required when Authentication Type is Session Login or Basic Auth. |
Yes |
Password used for Splunk session login or basic authentication. |
|
HEC Token |
No |
Yes |
Token used only for HTTP Event Collector requests. |

