[
https://issues.apache.org/jira/browse/JENA-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15791181#comment-15791181
]
Andy Seaborne commented on JENA-1230:
-------------------------------------
At Jena 3.1.1, the code switched to using the new Apache HttpComponents API. A
consequence is that setting up authentication is now done by the application
creating the right {{HttpClient}} rather than Jena internally modifying an
{{HttpClient}} (which is no supported by the new Apache HttpComponents API).
{{HttpAuthenticator}} has gone away; the way Jena was handling security can not
be done any more.
https://jena.apache.org/documentation/query/http-auth.html
That should mean the code in the example should work but needs to be run by the
application to build an {{HttpClient}}.
> Proxy authentication via NTLM does not work
> -------------------------------------------
>
> Key: JENA-1230
> URL: https://issues.apache.org/jira/browse/JENA-1230
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Reporter: Michael Sperber
> Attachments: NTLMProxyAuthenticator.scala
>
>
> Here:
> http://stackoverflow.com/questions/22461562/jena-proxy-authentication
> ... someones is trying to make Jena work with a proxy that requires NTLM
> authentication.
> As a result,
> https://issues.apache.org/jira/browse/JENA-658
> was created, which resulted in SimpleNTAuthenticator.
> However, that does work for proxy authentication, as the authenticator is
> scoped to the target host, not the proxy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
