Security

Storing encrypted credentials and retrieving them

Betelgeuse
Engager

So I've been looking at this blog post from 10 years ago:

https://www.splunk.com/en_us/blog/security/storing-encrypted-credentials.html

But what is outlined there does not seem to work. I have the following setup.xml file:

<setup>
<block title="Specify a Proofpoint token to access logs" endpoint="storage/passwords" entity="_new">
<input field="prooftoken">
<label>Proofpoint token</label>
<type>password</type>
</input>
</block>
</setup>

Per the blog post my token should be stored in app.conf and that is simply not the case.

I have a UI rendered asking me to specify a token (per the .XML above) but upon hitting save, I see no evidence of retention in any .conf file.

Labels (1)

gjanders
SplunkTrust
SplunkTrust
0 Karma

Brainizer
Explorer

Just had the same problem. What the documentation does not say is that the field values have to be "username" and "password". One can't define their own

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...