Unable to delete token for non-existent user

Available Languages

Updated:September 29, 2026
Document ID:SPLK048405

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise 9.1.3

Description

Splunk search head - unable to delete token - Could not get info for non-existent user="xyz123". This could happen for a previous user who was on an SHC is using single sign on / SAML, the user is no longer exists. And the token under this user cannot be disabled or removed.

A screenshot of this issue:


Investigation

This below workaround can help to delete the token:

Create a local user with the deactivated user's username. Then the token can be deleted through the UI. Once this can be done, the user can be deleted.

 


Resolution

A fix for resolution will be available in release 9.3.3 and 9.4.1. This will help to delete tokens for the users do not exist anymore. 

The root cause was identified by Engineering that the code did not recognize the request when the user is "could not get info for non-existing". Code fix will cover this scenario.

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products