cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <>
Subject [jira] [Commented] (CXF-6188) Authorization loop using "CurrentWindowsCredentials"
Date Wed, 07 Jan 2015 10:27:35 GMT


Colm O hEigeartaigh commented on CXF-6188:

Would it be possible for you to submit a (non quick-and-dirty) patch for this issue?


> Authorization loop using "CurrentWindowsCredentials" 
> -----------------------------------------------------
>                 Key: CXF-6188
>                 URL:
>             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
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) (Maven GAV is org.apache.httpcomponents/winauth-jni
> When I use (2), I get a "Authorization loop detected on Conduit" exception.
> See more in
> 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

View raw message