Storing and using passwords in a Custom Alert Action

[jack_burton]

I've got a set of custom alert actions that when invoked, will fire off a python script that (among other things) makes a REST call out to a server that requires authentication.

As part of the design, I've defined a global configuration page (setup.xml) that will take in a username, and a secret value password. What I'd like to do is have that password stored securely, and then retrieved in my script, appended to the username, and base64'd to be included in the basic auth. header of my REST call.

What is the best practice for taking as a global input a password, storing those credentials, and then retrieving those credentials as part of a custom alert action? Thanks!

[richgalloway · Accepted solution]

George Starcher has an excellent blog post on this subject. See http://www.georgestarcher.com/splunk-stored-encrypted-credentials/

[ttam_splunk]

If the original link doesn't load, the Way Back Machine has an archive here https://web.archive.org/web/20210417061309/http://www.georgestarcher.com/splunk-stored-encrypted-cre...