Getting Data In

user-seed.conf - does the file disappear after use?

rewritex
Contributor

Hello,
We have utilized the user-seed.conf correctly and it worked fine a couple months ago but we just noticed that the user-seed.conf file has disappeared. In reading the documentation it states "Use this file to create an initial login." so we are guessing its a sort of one-time use file and is removed. We want to have the file stay around longer so we can integrate it into scripts so the plan is to just put the contents into another file that will not disappear.

Q: Is or does the user-seed.conf disappear after use?

Thanks,
Sean

0 Karma
1 Solution

griersoncrick
Explorer

Yes, user-seed.conf disappears after it is used.

If you want to create a script that uses it, one option is to output the text file from the script into the correct location as part of the script, containing a hashed password.

We use Ansible in our environment, and push a templated user-seed.conf, but a script or other config management tool should do the same..

View solution in original post

0 Karma

griersoncrick
Explorer

Yes, user-seed.conf disappears after it is used.

If you want to create a script that uses it, one option is to output the text file from the script into the correct location as part of the script, containing a hashed password.

We use Ansible in our environment, and push a templated user-seed.conf, but a script or other config management tool should do the same..

0 Karma
Get Updates on the Splunk Community!

Enter the Dashboard Challenge and Watch the .conf24 Global Broadcast!

The Splunk Community Dashboard Challenge is still happening, and it's not too late to enter for the week of ...

Join Us at the Builder Bar at .conf24 – Empowering Innovation and Collaboration

What is the Builder Bar? The Builder Bar is more than just a place; it's a hub of creativity, collaboration, ...

Combine Multiline Logs into a Single Event with SOCK - a Guide for Advanced Users

This article is the continuation of the “Combine multiline logs into a single event with SOCK - a step-by-step ...