[
https://issues.apache.org/jira/browse/CXF-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267492#comment-14267492
]
Colm O hEigeartaigh commented on CXF-6188:
------------------------------------------
Would it be possible for you to submit a (non quick-and-dirty) patch for this
issue?
Colm.
> Authorization loop using "CurrentWindowsCredentials"
> -----------------------------------------------------
>
> Key: CXF-6188
> URL: https://issues.apache.org/jira/browse/CXF-6188
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.3
> Environment: All Windows versions
> Reporter: Hans Schuell
> Priority: Blocker
>
> It is actually not possible to use
> org.apache.http.impl.auth.win.CurrentWindowsCredentials to build a CXF client
> for a WCF service that is using NTLM authentication.
> When accessing a web service, that is defined in C# using:
> binding.Security.Transport.ClientCredentialType =
> HttpClientCredentialType.Ntlm;
> it is possible to setup a CXF client with explicitly defined credential by
> using
> (1) org.apache.http.auth.NTCredentials
> but not with
> (2) org.apache.http.impl.auth.win.CurrentWindowsCredentials (Maven GAV is
> org.apache.httpcomponents/winauth-jni /4.3.6)
> When I use (2), I get a "Authorization loop detected on Conduit" exception.
> See more in
> http://cxf.547215.n5.nabble.com/Authorization-loop-using-quot-CurrentWindowsCredentials-quot-td5752751.html
> The patch I made and described in the mailing list question is a
> quick-and-dirty solution for me to see, whether it would work from a
> technical perspective. The hard-coded
> .setDefaultAuthSchemeRegistry(...)
> .setDefaultCredentialsProvider(...)
> must be sth. thta can be passed to AsyncHTTPConduit.
> If you need the WCF service or the Java code , it can be provided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
