Reload 4 Auth
| Topics: | CLI, api, dev, hacks, tech |
|---|---|
| Tags: | |
| Share: |
This will be a very brief post, to fulfill my obligations. I’ll share something a little more informative, perhaps even more interesting, in an upcoming post (soon… I promise (kinda) this time).
As of Splunk 4.0, our old somewhat-of-an-API has been replaced with an entirely new REST API, invalidating my old post on reloading authentication from the command line.
Sooo….. in 4.x, you can restart the authentication system with the following command:
$ splunk _internal call /authentication/providers/services/_reload -auth admin:changeme
Any errors should be obvious in the resulting XML. As of 4.0.3, you’ll also get a non-zero return code upon receiving errors from the API. And I’ve filed a bug (just now) to expose this as a real CLI command, so soon this post will no longer be very important. 
Happy now, Simeon?
August 20th, 2009 at 12:57 pm
Cool trick, what other things can this command do?
August 20th, 2009 at 1:50 pm
Can you also do a post on reloading file inputs with splunk _internal call /services/data/inputs/monitor/_reload -auth admin:changme, and then file a bug to expose it as a real CLI command?
August 28th, 2009 at 7:52 am
Would a reload authentication work with LDAP in version 4.x ? With version 3.10, I had to restart Splunk each time I added a user as reload auth would not work - guess that’s because of the way Splunk works with LDAP .
August 28th, 2009 at 10:11 am
Indraneel, it looks like reloading auth will cause Splunk to update its list of LDAP users. Let us know if this doesn’t appear to work for you in 4.x.
August 28th, 2009 at 10:28 am
Thanks Amrit. Yes it did work on 4.x .
August 28th, 2009 at 10:30 am
Great!
September 16th, 2009 at 10:15 am
Some genius decided to simply the command. It is now, ./splunk reload auth
http://www.splunk.com/base/Documentation/4.0.3/ReleaseNotes/CLIChanges
September 16th, 2009 at 10:23 am
Note that Tina’s comment only applies to 4.0.4 and beyond…