[
https://issues.apache.org/jira/browse/HTTPCLIENT-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102251#comment-14102251
]
Ka-Lok Fung commented on HTTPCLIENT-1545:
-----------------------------------------
The likely reason why it isn't failing is because {{InitializeSecurityContext}}
in {{getToken}} isn't causing a {{Win32Exception}} to be thrown.
By any chance is your Windows machine not joined to a domain, i.e., it's a
member of WORKGROUP? Also, what version of Windows are you using?
I'll try to replicate the issue on a virtual machine that matches the
conditions you specified. In the end, I might be forced to add a JUnit
assumption that the test can only run on Windows machines that is a member of a
domain.
> Possible infinite loop when WindowsNegotiateScheme authentication fails
> -----------------------------------------------------------------------
>
> Key: HTTPCLIENT-1545
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1545
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.4 Alpha1
> Environment: Windows
> Reporter: Ka-Lok Fung
> Fix For: 4.4 Alpha2
>
> Attachments: HTTPCLIENT-1545.patch.diff
>
>
> When {{WindowsNegotiateScheme}} authentication fails, it's possible for
> HttpClient to retry the authentication in an endless loop because the
> {{continueNeeded}} flag is not set to {{false}} when authentication fails.
> One possible way of causing authentication to fail is to use a service
> principle name that is outside your Windows domain (e.g., HTTP/EXAMPLE.COM).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
