When Splunk is configured with SAML authentication, attempting to delete a user via the Splunk Web interface does not successfully remove the user from the system.
For example, executing the following REST API command removes the user from the local passwd file, but the user still appears in the Splunk User Interface as a SAML user:
curl -k -u admin:<password> --request DELETE https://<search_head>:8089/services/authentication/users/<user_to_be_deleted>
Additionally, attempts to modify user permissions or roles for a SAML-authenticated user via the Splunk Web interface may appear to save successfully, but the changes do not persist.
This occurs because SAML user attributes and roles are managed externally by the Identity Provider (IdP). For IdPs that do not support SAML Attribute Query Requests (such as Azure Entra ID), Splunk caches the role information from the initial SAML assertion in the UserInfoCache for the duration of the session. Splunk does not automatically re-evaluate role mappings unless a new SAML assertion is processed or the cache is manually cleared.
To determine if the issue is related to the user type, verify whether the user is a Local user or a SAML-authenticated user:
| rest /services/authentication/users
| search users=<user_in_question>
| table title type roles
| rename title as username type as authentication_type
If the user is identified as a SAML user, the Splunk Web interface will not allow local modifications to their roles or permanent deletion of the user account.
Perform the following steps:
To modify roles or permissions for a SAML user:
To permanently remove a SAML user from the Splunk environment:
$SPLUNK_HOME/bin/splunk reload auth
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |