This error could be caused by a few things, do you have updated protocol? Do you have all the certs required? Are you actually routing through a proxy? Are there any more errors than that? ... View more

There should be an error in splunkd when you get redirected to unauthorized that states what user it was trying to log in as. Also if you changed it from samaccountname to userprincipalname you will have to modify it on the AD/ADFS side as well. ... View more

Currently the above fix is only for Microsoft ADFS, but it is possible using Okta and F5 using the SAML configuration with the prompt being on the IdP side. What is your IdP? ... View more

For web.conf Change the AuthMethod, and add the PivOid list certBasedUserAuthMethod = PIV certBasedUserAuthPivOidList = 1.3.6.1.4.1.311.20.2.3, Microsoft Universal Principal Name ... View more

The value for userNameAttribute needs to be userPrincipalName to match the value being extracted from the CAC ... View more

Anything above 9.2.2 will have the fix, so you should be fine with 9.3. What is the value you are using for userNameAttribute in authentication.conf? ... View more

If you are Army you need to be on versions 9.0.10, 9.1.5, or 9.2.2 There was a bug that was fixed and pushed on 7/1/2024 ... View more