-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Waffle SpringBoot error logging - Invalid Authorization header: Negotiate #1472
Comments
It looks like you have a |
What we have discovered is that this was working perfectly fine till we upgraded the version of the Waffle dependency -> waffle-spring-boot-starter to 3.0.0 for our Spring Boot application. Prior to this, we were using version 2.2.1 when such runtime exceptions didn't appear ever before. Is there something in 3.0.0 for us to configure anything additionally? |
@Smaju78 Does 2.3.0 work? 2.2.1 is really old at this point, so I think working your way up to confirm what works or does not will help you isolate the issue. I agree with @dblock here on missing token. I saw something online referring to that occuring when crossing domains but not sure if that is related. The code in that specific spot hasn't changed since it was originally written to any degree. It expects the protocol + space + token. The space and token are missing here. |
I had the same issue. I found out that the service responded with 401 even after the user had been successfully authenticated causing Chrome to send a Negotiate Authorization header without a token which, apparently, is incorrect behavior according to the protocol spec. Anyway, the reason for the 401 response seemed to be that the NegotiateSecurityFilter was applied twice. So making sure that the filter was only applied once solved the issue for me. The fix in the library would probably be to have the |
Our application uses Waffle SpringBoot starter to identify the Active Directory user for user authentication of our application. However, everytime a user logs in, there is an error logged though it does not prevent authentication. This has resulted in ballooning of the log file very soon to 100s of MBs. The error I am getting is as follows
I have tried to filter this error from being printed in Log4J2 by using RegexFilter on waffle.util.* but that has also not worked.
I need help to figure
If this error is indicative of any wrong configuration?
If not, how to turn off printing this error in log files using Log4J2?
The text was updated successfully, but these errors were encountered: