Encountered the following error while trying to update: In handler 'localapps': Error while posting to url=/servicesNS/nobody/radius_auth/admin/radius_auth/default. Found the following information in the _local index but am not sure what it means:
2014-09-09 09:59:50,167 ERROR RadiusAuthRestHandler - Exception generated while performing edit
Traceback (most recent call last):
File "/scratch/splunk/etc/apps/radius_auth/bin/radius_auth_rest_handler.py", line 546, in handleEdit
cleaned_params = RadiusAuthRestHandler.checkConf(new_settings, name, confInfo, existing_settings=existing_settings)
File "/scratch/splunk/etc/apps/radius_auth/bin/radius_auth_rest_handler.py", line 639, in checkConf
validator.validate( stanza, cleaned_params, existing_settings )
File "/scratch/splunk/etc/apps/radius_auth/bin/radius_auth_rest_handler.py", line 164, in validate
raise admin.ArgValidationException("Unable to validate credentials against the server '%s' for user '%s'" % ( values['server'], values['test_username']))
ArgValidationException: Unable to validate credentials against the server 'srv-aaa01sj.cadence.com' for user 'lbogle'
That error means that the RADIUS tried to test the configuration was unable to authenticate to the RADIUS server. Most likely this is due to something in configuration that prevents the app from authenticating (incorrect key, IP address restriction on server, etc.).
BTW: the app used to provide a nice message in the setup page indicating that the test authentication failed but this no longer works due to a bug in Splunk (which they are going to fix in a later release of Splunk).
That error means that the RADIUS tried to test the configuration was unable to authenticate to the RADIUS server. Most likely this is due to something in configuration that prevents the app from authenticating (incorrect key, IP address restriction on server, etc.).
BTW: the app used to provide a nice message in the setup page indicating that the test authentication failed but this no longer works due to a bug in Splunk (which they are going to fix in a later release of Splunk).