[
https://issues.apache.org/jira/browse/CXF-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467612#comment-13467612
]
Oleg Kalnichevski commented on CXF-4525:
----------------------------------------
Shaun
This has nothing to do with CXF, but just for the record, I would like to
mention the following: based on our experience JCIFS has absolutely the best
implementation of an NTLN authentication engine. Moreover, we actually
recommend using JCIFS instead of our own internal implementation as long as its
LGPL licence is not an issue [1]. I am also quite sure JCIFS is not specific to
Windows platforms.
Oleg
[1] http://hc.apache.org/httpcomponents-client-ga/ntlm.html
> expose http client, allow for NTLM authentication
> -------------------------------------------------
>
> Key: CXF-4525
> URL: https://issues.apache.org/jira/browse/CXF-4525
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.7.0
> Reporter: Shaun Elliott
> Assignee: Daniel Kulp
> Fix For: 2.7.0
>
>
> The class: CXFAsyncRequester hides the DefaultHttpAsyncClient, thus
> preventing interaction from outside classes. One use case would be to
> leverage the embedded DefaultHttpAsyncClient to do NTLM authentication, which
> is currently not possible with CXF.
> AsyncHTTPConduit will also need a getter on the factory field.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
