[CXF-6188] Authorization loop using "CurrentWindowsCredentials"

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.0.3
• Fix Version/s: 3.0.4
• Component/s: Core

Environment

All Windows versions

• Estimated Complexity: Unknown
• Assignee: Daniel Kulp
• Reporter: Hans Schuell
• Created: 06/Jan/15 18:25
• Updated: 16/Feb/15 16:09
• Resolved: 09/Jan/15 17:28

Description

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.