Splunk Apps » RADIUS Authentication

{{>toc}}

h1. Troubleshooting

h2. User Accounts from the RADIUS Server Cannot Log In

This can be due to a number of issues. View the related logs with the following search to determine why users cannot log in:

<pre>

index=_internal ( (UserManagerPro OR HTTPAuthManager) AND sourcetype="splunkd" ) OR sourcetype="radius_auth*"

</pre>

h2. Roles are Not Being Loaded from the RADIUS Server

Incorrect vendor code or attribute ID is the most common reasons for roles not being loaded from the RADIUS server. Use the following search to view the attributes that are loaded when a user successfully authenticates (note that you will need to successfully login using a RADIUS server user to see the attributes):

<pre>

index=_internal "Received the following fields upon login" sourcetype="radius_auth"

</pre>

h2. Splunk is Still Using the Credentials from my Local Account

Users will be authenticated via RADIUS _unless_ they have a local account. Splunk gives local accounts priority over scripted auth users and therefore will not use RADIUS for accounts where a local account already exists.

h2. Authentication Test on Setup Screen Fails Indicating "Unable to validate credentials against the server ..."

The logs likely provide more details regarding why the authentication attempt failed. You can see the relevant logs by searching for the sourcetype "radius_auth" in the internal index:

    index=_internal sourcetype="radius_auth"

The log message will probably look something like "Exception triggered when attempting to contact the RADIUS server" and should include details regarding why the authentication attempt failed.

h2. The Setup Screen Fails Indicating That The REST Handler Failed (on Splunk 6.0+)

This is due to a bug in Splunk which causes it to no longer tell users that the input was invalid. Most likely, something is wrong with the input. Likely problems are: the test user account information could not validate (if provided) or the attribute ID for getting the roles information is incorrect.

h2. I have users listed in Splunk that no longer exist; how do I remove them?

The RADIUS app has no way to know whether or not users have been removed. This means you may have users listed in Splunk that could no longer authenticate (since the RADIUS would reject them) but still appear in the user list. These can be removed by using the clearradiuscache search command that is included with version 1.4 and later.

To use it, assign the necessary user account the permission "clear_radius_user_cache" or use an account with "admin_all_objects".

Next, run the search command to clear the cache of the given users. You can run it on individual user accounts or you can have the command delete entries for users that have not authenticated for a certain time.

Below is an example that drops users that have not authenticated within the last 30 days:

<pre>

| clearradiuscache days_ago=30

</pre>

You can also run a test just to see what entries the command would remove before running it:

<pre>

| clearradiuscache days_ago=30 test=1

</pre>

You can also remove a particular users from the list too:

<pre>

| clearradiuscache user="bob"

</pre>

The user will not be removed from the user's list instantly. Just wait for a few minutes them to be removed.

It is important to note that removing an entry from the cache does not prevent them from re-authenticating. Instead, it just prevents Splunk from listing them in the user list (until they authenticate again).

Furthermore, a saved-search is included which will remove the entries automatically once a user has not authenticated within 90 days. You can modify the search to purge entries if you want it to remove entries quicker (like after 30 days of inactivity). See the search titled "Prune Old RADIUS Cache Entries". Note that cached entries created by the RADIUS app before version 1.4.0 do not have the date of last login and will need to be manually removed by username (e.g. '| clearradiuscache user="bob"')