Getting Data In

Creating service account in splunk to re-assign the orphaned knowledge object

man03359
Communicator

Hi,

I am a splunk admin and we are re-assigning the orphaned knowledge object to my name as a temporary solution. I need to create a service account so that I can assign the orphaned knowledge objects to that account. I am doing it for the first time. Could some one please  specify what roles and capacities I should assign. Also is it the same process to create a service account same as how we create a local user in splunk like Settings > Users > Create User

 

ps. I am on splunk cloud | version: 9.3

Labels (1)
0 Karma
1 Solution

livehybrid
SplunkTrust
SplunkTrust

Hi

Yes, creating a service account in Splunk Cloud is the same as creating a local user via Settings > Users > Create User.

  • Roles: Assign the minimum privileged role for the service account own and manage the required knowledge objects, run searches etc. Optionally, create a custom role dedicated for the service user.
  • App context: Ensure the role has write permissions on relevant apps where knowledge objects reside.

This service account will then be a stable owner for orphaned knowledge objects, avoiding future orphaning if admins or users who own the KOs were to leave.

  • Use a strong, unique password and store it securely.
  • Document the account purpose and ownership internally.

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

View solution in original post

livehybrid
SplunkTrust
SplunkTrust

Hi

Yes, creating a service account in Splunk Cloud is the same as creating a local user via Settings > Users > Create User.

  • Roles: Assign the minimum privileged role for the service account own and manage the required knowledge objects, run searches etc. Optionally, create a custom role dedicated for the service user.
  • App context: Ensure the role has write permissions on relevant apps where knowledge objects reside.

This service account will then be a stable owner for orphaned knowledge objects, avoiding future orphaning if admins or users who own the KOs were to leave.

  • Use a strong, unique password and store it securely.
  • Document the account purpose and ownership internally.

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...