[
https://issues.apache.org/jira/browse/HTTPCLIENT-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481157#comment-17481157
]
can commented on HTTPCLIENT-2199:
---------------------------------
> I also can see the three-way NTLM handshake correctly executed.
I think you checked this file "RequestAfter2ndResponse.txt". It is using
external NTLM scheme which I fixed (so three-way ntlm handshake is working
properly there).
You should check this file "NoRequestAfter2ndResponse.txt". Here, 3rd GET
request is not being sent. This is how it behaves right now on v5.1.2.
> NTLM scheme can have no parameters. It has a single opaque challenge value.
Actually you are right. But if you check this screenshot
[^13039297_150694519-4216bb91-ad43-40d1-ba8e-1818af685560.png], here you can
see debug variables. authChallenge param variable contains "opaque challenge
value" but value variable is null.
And NTLMScheme object is trying to read value field. That's why authentication
is failing at this step.
> NTLM auth is failing while processing 2nd challenge response
> ------------------------------------------------------------
>
> Key: HTTPCLIENT-2199
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2199
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 5.1.2
> Reporter: can
> Priority: Major
> Attachments: 150694519-4216bb91-ad43-40d1-ba8e-1818af685560.png,
> NoRequestAfter2ndResponse.txt, RequestAfter2ndResponse.txt
>
>
> In NTLMScheme class (NTLMScheme.java), processChallenge function is trying to
> read challenge using getValue() function.
> But it is always returning null.
> Challenge is actually stored inside params and can be accessed by getParams()
> function.
> see [^150694519-4216bb91-ad43-40d1-ba8e-1818af685560.png]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
