[
https://issues.apache.org/jira/browse/CXF-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976764#comment-13976764
]
Jayashankar commented on CXF-5671:
----------------------------------
But are you certain that NTLM hand shake is happening as expected ? Where in my
case, the type 3 hand shake is taking my system credentials and ultimately
failing. The consumer is with JDK 6.
This is the authorization header going
TlRMTVNTUAADAAAAGAAYAIIAAAAIAQgBmgAAAAoACgBYAAAACgAKAGIAAAAWABYAbAAAAAAAAACiAQAABYKIogYBsR0AAAAP2ZThXptXCah8dUBtXbZooVIAUABFAEcAQQBrAGEAcgBuAGoAVwBLAEEAUgBOAEoAVwA3AEgAWQBEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP4BHTokKCu5xdtzrzC
I actually gave Username = te
password = Testeng!
> 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)
