Skip to main content

Splunk

Connection

Setup

Klef reaches Splunk’s management port, 8089, with an authentication token.
1
Turn on token authentication, if it is off: in Splunk Web, go to Settings, then Tokens, and choose Enable Token Authentication.
2
Choose New Token, and make it for a user whose role holds the edit_user and list_users capabilities, such as admin. Set an expiry you will remember to renew.
3
Copy the token into Klef, with your management URL, such as https://splunk.acme.com:8089. On Splunk Cloud Platform, the URL is https://<stack>.splunkcloud.com:8089, and Klef’s addresses must be on the stack’s allow list for the management port.
The management port’s certificate must be one a browser trusts. Klef refuses Splunk’s default self-signed certificate. Klef manages the users an admin or LDAP already made, since Splunk needs a password to make a user. Splunk has no disabled user, so switching a user off deletes them. SAML users are not Splunk users, so Klef does not list them. Their roles come from your identity provider’s groups.

Settings

splunk.user

Fields

Default Account Matching Rules

When Klef adopts an account that already exists in Splunk, it works out whose it is by trying these in order. A connection can override them.

Examples

Splunk users

Keeps each engineer’s Splunk user named and emailed, and deletes it when they leave.