pass4symkey management in splunk-docker
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 549
- Forks
- 277
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 2
Description
Hi all,
I'm struggling to find out how to get the current pass4SymKey (decrypted) on my dockerised splunk instance, and in general how to manage it (can I change it with a line in defaults.yaml for example?). Can anyone point me in the right direction?
I tried getting it on a container with:
$SPLUNK_HOME/bin/splunk show-decrypted --value '<pass4symkey>'
But just got:
Warning: cannot create "/opt/splunk/var/log/splunk"
Warning: cannot create "/opt/splunk/var/log/introspection"
Warning: cannot create "/opt/splunk/var/log/watchdog"
<pass4symkey>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the defaults.yaml configuration and the $SPLUNK_HOME/bin/splunk show-decrypted command shown in the report. Determine the supported way to retrieve and change pass4SymKey in a Dockerized Splunk instance, including the cause of the reported directory warnings. Done means the documented procedure and configuration limits are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100