Is it Automatic Query Retry?
I have lots of these errors in splunkd.log
:
WARN UserManagerPro - AQR not supported and user=nobody information not found in cache
AQR= attributeQueryRequest
Look at authentication.conf. spec page and remove the ones that are AQR specific, then reload auth. That may help with the "AQR not supported" messages. typically what happens is the password manager will fill in a username/password, and it'll try to query AQR when the IdP doesn't support it.,AQR = Attribute Query Response
look at authentication.conf. spec page and remove the ones that are AQR specific, then reload auth. That may help with the "AQR not supported" messages
typically what happens is their password manager will fill in a username/password, and it'll try to query AQR when the IdP doesn't support it.
AQR= attributeQueryRequest
Look at authentication.conf. spec page and remove the ones that are AQR specific, then reload auth. That may help with the "AQR not supported" messages. typically what happens is the password manager will fill in a username/password, and it'll try to query AQR when the IdP doesn't support it.,AQR = Attribute Query Response
look at authentication.conf. spec page and remove the ones that are AQR specific, then reload auth. That may help with the "AQR not supported" messages
typically what happens is their password manager will fill in a username/password, and it'll try to query AQR when the IdP doesn't support it.
I am experiencing this while trying to save the configuration for the Cisco eStreamer app. Error = -0800 WAN UserManagerPro - AQR not supported and user=nobody information not found in cache.
Really need this app to work
Thank you
Some 3rd party company that provides Panda, perhaps?
https://docs.splunk.com/Documentation/MLApp/2.4.0/User/Thirdpartysoftwarecredits
I'm not sure Panda is involved in user management, is it?