Do not handle NTLM authentication requests #43
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoid handling NTLM authentication requests in the SpnegoAuthenticationProcessingFilter, since the payload is not a valid Spnego token.
These tokens are currently treated as a SpNego token and passed to the GSSAPI, which throws an exception
GSSException: Defective token detected (Mechanism level: GSSHeader did not find the right tag)
.Depending on the error handler, IE may think that it successfully authenticated via NTLM and/or continue to sent NTLM tokens on subsequent requests.
IE also likes to preemtively send NTLM tokens when posting forms (i.e. instead of posting a FORM with the actual data, it sends a zero-byte POST with an NTLM header, expects the server to issue an NTLM challenge and will ultimately retry the POST once it's confident that it's authorized.
This breaks badly when servers don't actually implement NTLM authentication.