> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Splunk (Users and Roles)

> Connect Splunk with a token, hostname and port so Lumos syncs Splunk users, roles and last login for Access Reviews. This connection doesn't send Lumos events to Splunk.

*This article covers the Splunk connection that syncs Splunk users and roles into Lumos. It doesn't send Lumos events to Splunk. To stream Lumos events into a Splunk HTTP Event Collector, see [Splunk (SIEM)](https://docs.lumos.com/integrations/library/splunk-siem.md).*

## After this article

You'll be able to connect Splunk to Lumos to sync Splunk users, their roles and their last login, and to tell this connection apart from the Splunk SIEM connection.

## Which Splunk card to use

Both Splunk cards in **"Integrations"** are named **Splunk**. On the **"Discover"** tab, check the category.

| Category | What it does | Fields when you connect |
| - | - | - |
| **"IT & Security"** | Syncs Splunk users and roles into Lumos (this article) | **"Token"**, **"Hostname"**, **"Port"** |
| **"Marketing & Analytics"** | Sends Lumos events to your Splunk HTTP Event Collector ([Splunk (SIEM)](https://docs.lumos.com/integrations/library/splunk-siem.md)) | **"Host"**, **"Token"** |

The user and role sync card also lists **"Find Activity"** under capabilities and **"Roles"** under entitlement types. The SIEM card lists neither.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Users | Account | Yes | No | Splunk user accounts. Splunk's API doesn't report whether a user is disabled, so every synced user shows as active |
| Roles | Permission | Yes | No | The roles assigned to each user |

Activity tracking is supported. Lumos reads each user's last successful login.

## Required plan and roles

There's no minimum Splunk plan. Token authentication must be turned on in Splunk, and the user the token belongs to needs to be able to read all users and roles through the Splunk REST API.

## Instructions

**Phase 1: Create a token in Splunk**

1. Log in to Splunk Web and go to **"Settings"** > **"Users and Authentication"** > **"Tokens"**.
2. If token authentication is turned off, turn it on.
3. Create a new token, fill in the token details including an expiration date, and copy the token Splunk displays. When the token expires, reconnect with a new one.

**Phase 2: Connect in Lumos**

1. In **"Integrations"**, open the **"Discover"** tab and pick the Splunk card in the **"IT & Security"** category, or reconnect it from your connected integrations.
2. Enter the token in **"Token"**.
3. Enter your Splunk management hostname in **"Hostname"**, without `https://`. For Splunk Cloud this looks like `prd-p-9f604.splunkcloud.com`. For Splunk Enterprise, use your server's hostname or IP address.
4. Leave **"Port"** at `8089` unless your Splunk REST API listens on a different port.
5. Connect the integration.

## API Endpoints Used

> [!NOTE]
>
> The API endpoints this integration uses are available to logged-in Lumos customers. Log in to view them.

## Troubleshooting

**Users still show as active after you disable them in Splunk.** Splunk's REST API doesn't expose a disabled state, so Lumos reports every Splunk user it finds as active.

**The connection fails or times out.** Check that **"Hostname"** holds your Splunk management hostname, not the HEC host that starts with `http-inputs` and belongs to the SIEM connection. Then confirm that port 8089, or the port you entered, accepts connections from Lumos.
