• Troubleshooting
  • User Accounts from the RADIUS Server Cannot Log In
  • Roles are Not Being Loaded from the RADIUS Server
  • Splunk is Still Using the Credentials from my Local Account
  • Authentication Test on Setup Screen Fails Indicating "Unable to validate credentials against the server ..."
  • The Setup Screen Fails Indicating That The REST Handler Failed (on Splunk 6.0)

Troubleshooting¶

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:

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

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):

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

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.

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.

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.