[
https://issues.apache.org/jira/browse/CXF-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976838#comment-13976838
]
Sergey Beryozkin commented on CXF-5671:
---------------------------------------
Well, this issue about not being possible to affect NTLM with AsyncHttpConduit
and as we've confirmed AsyncHttpConduit does take custom Credentials (ex,
NTCredentials) into the consideration. So I think this issue can be resolved.
I've no idea why the actual handshake fails. Does it work for you if you use
HttpClient directly ?
Here are the relevant versions used by CXF 3.0.0 milestone2:
<cxf.httpcomponents.asyncclient.version>4.0.1</cxf.httpcomponents.asyncclient.version>
<cxf.httpcomponents.client.version>4.3.3</cxf.httpcomponents.client.version>
<cxf.httpcomponents.core.version>4.3.2</cxf.httpcomponents.core.version>
> NTLM API not exposed
> --------------------
>
> Key: CXF-5671
> URL: https://issues.apache.org/jira/browse/CXF-5671
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS Security
> Affects Versions: 3.0.0-milestone2
> Environment: Tomcat 6, jdk (1.6 and 1.7)
> Reporter: Jayashankar
>
> NTLM API using AsyncHTTPConduit is deprecated in cxf 3.0 milestone 2 release,
> where as it is working in 2.7.7.. It is affecting backward compatibility and
> there is no proper API to refactor.
> HTTPConduit http = (HTTPConduit)client.getConduit();
> if ( http instanceof AsyncHTTPConduit ) {
> AsyncHTTPConduit conduit = (AsyncHTTPConduit)http;
> DefaultHttpAsyncClient defaultHttpAsyncClient = null;
> try {
> defaultHttpAsyncClient = conduit.getHttpAsyncClient();
> } catch (IOException e) {
> // TODO Auto-generated catch block }
>
> defaultHttpAsyncClient.getCredentialsProvider().setCredentials(
> AuthScope.ANY, new NTCredentials( "user", "pwd", "host", "domain" ) );
>
> conduit.getClient().setAllowChunking( false );
> conduit.getClient().setAutoRedirect( true );
> }
--
This message was sent by Atlassian JIRA
(v6.2#6252)
