One admin user cannot use the particular REST endpoint
| rest splunk_server=local /services/admin/SAML-groups
audit.log
Audit:[timestamp=02-04-2025 20:28:38.831, user=a123456, action=search, info=completed, search_id='1738700894.976564_E7F2D3C1-5A8B-4C7D-9E6F-0A1B2C3D4E5F', has_error_warn=true, fully_completed_search=true, total_run_time=0.22, event_count=0, result_count=0, available_count=0, scan_count=0, drop_count=0, exec_time=1738700895, api_et=1738612800.000000000, api_lt=1738700894.000000000, api_index_et=N/A, api_index_lt=N/A, search_et=1738612800.000000000, search_lt=1738700894.000000000, is_realtime=0, savedsearch_name="", search_startup_time="1015", is_prjob=false, is_flex_search=false, rate_limit_retry_enabled=false, acceleration_id="D4C3B2A1-5E6F-7A8B-9C0D-1E2F3A4B5C6D_BE_e7f29b3_55dd471cae8b6f9e", app="BE", provenance="UI:Search", mode="historical", is_proxied=false, searched_buckets=0, eliminated_buckets=0, considered_events=0, total_slices=0, decompressed_slices=0, duration.command.search.index=0, invocations.command.search.index.bucketcache.hit=0, duration.command.search.index.bucketcache.hit=0, invocations.command.search.index.bucketcache.miss=0, duration.command.search.index.bucketcache.miss=0, invocations.command.search.index.bucketcache.error=0, duration.command.search.rawdata=0, invocations.command.search.rawdata.bucketcache.hit=0, duration.command.search.rawdata.bucketcache.hit=0, invocations.command.search.rawdata.bucketcache.miss=0, duration.command.search.rawdata.bucketcache.miss=0, invocations.command.search.rawdata.bucketcache.error=0, roles='admin+abc_admin+cde_salesforce+fgh-user+123team+456user+can_delete+it_admin+it_analyst+it_team_admin+it_user+kv_admin+metric_ad_admin+ijk_user+power+restricted-default-user+splunk-power-user+user+user_ad_user', search='| rest splunk_server=local /services/admin/SAML-groups', is_federated_search=0, is_fsh_remote_search=0]
search_messages.log
02-04-2025 20:28:38.831 +0000 ERROR SearchMessages - orig_component="SearchOperator:rest" app="BE" sid="1738700894.976564_E7F2D3C1-5A8B-4C7D-9E6F-0A1B2C3D4E5F" message_key="RESTPROC:REST_BAD_URI_PATH" message=phase_0 - Failed to fetch REST endpoint uri=https://127.0.0.1:8089/services/admin/SAML-groups?count=0 from server https://127.0.0.1:8089. Check that the URI path provided exists in the REST API.
02-04-2025 20:28:38.831 +0000 ERROR SearchMessages - orig_component="SearchOperator:rest" app="BE" sid="1738700894.976564_E7F2D3C1-5A8B-4C7D-9E6F-0A1B2C3D4E5F" message_key="RESTPROC:REST_STATUS_NOT_OK" message=phase_0 - The REST request on the endpoint URI /services/admin/SAML-groups?count=0 returned HTTP 'status not OK': code=500, Internal Server Error.
02-04-2025 20:28:38.831 +0000 WARN SearchMessages - orig_component="SearchOperator:rest" app="BE" sid="1738700894.976564_E7F2D3C1-5A8B-4C7D-9E6F-0A1B2C3D4E5F" message_key="" message=phase_0 - Unexpected status for to fetch REST endpoint uri=https://127.0.0.1:8089/services/admin/SAML-groups?count=0 from server=https://127.0.0.1:8089 - Internal Server Error
A finding show that the user has a couple of roles that don’t exist:
02-12-2025 01:02:49.176 +0000 ERROR AuthorizationManager [37960 TcpChannelThread] - Could not get info for role that does not exist: deleted-role-example01
02-10-2025 04:34:25.197 +0000 WARN AuthorizationManager [8455 SavedSearchFetcher] - Unknown role 'deleted-role-example02'
Removing the non-existent roles:deleted-role-example01 and deleted-role-example02 from the user under stanza [userToRoleMap_SAML] in authentication.conf:
[userToRoleMap_SAML]
a123456 = admin;cde_salesforce;fgh-user;123team;456user;deleted-role-example01;it_user;restricted-default-user;deleted-role-example02::David,Smith::David.Smith@abc.edf.com
The user then can access to the REST endpoint after this manual removal.
Further analysis found that the root cause was that a role mapping is still in authentication.conf after the role is removed from the authorize.conf:
authentication.conf
deleted-role-example01 = SAML-groups-example01
If the role is deleted in the authoriz.conf, but not role mapping is not removed in the authentication.conf, then the user's role can be re-appeared after the SAML user login. So the correct way to remove roles and to avoid the role mapping coming back to the user is to remove the relevant lines in both authorize.conf and authentication.conf:
authentication.conf
#deleted-role-example01 = SAML-groups-example01authorize.conf
#[deleted-role-example01]
Currently this requires manual edit in authentication.conf. A feature request was raised in this site: https://ideas.splunk.com/ideas/EID-I-2507
This feature request proposed an idea of the removal of "extra" roles from the authentication.conf to be fully automated by Splunk. If the user logs in and the role no longer exists in Splunk, it should automatically be removed from authentication.conf.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |