You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2009/07/01 00:56:47 UTC
[jira] Updated: (IVY-1094) Problem with NTLM proxy authentication
[ https://issues.apache.org/jira/browse/IVY-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene updated IVY-1094:
-------------------------------
Fix Version/s: (was: trunk)
2.1.0-RC2
> Problem with NTLM proxy authentication
> --------------------------------------
>
> Key: IVY-1094
> URL: https://issues.apache.org/jira/browse/IVY-1094
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.1.0-RC1
> Reporter: Mathieu Anquetin
> Assignee: Maarten Coene
> Fix For: 2.1.0-RC2
>
> Attachments: HttpClientHandler.txt
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I had problems to resolve and retrieve artifacts from an IBiblio Resolver. I was behind a corporate proxy and even if this proxy was correctly configured in Ivy, I was permanently denied access.
> After looking at the HttpClientHandler source code, I found that this was due to a lack of support for NTLM authentication. So I added this behavior in the submitted patch trying not to break the original behavior.
> Now, Ivy supports NTLM authentication if -Dhttp.proxyRealm=<your_domain> is set in ANT_OPTS. I could not test Basic Authentication but it seems to work also. Maybe someone can confirm ?
> Moreover, in order to avoid breaking an old bug, I put NTLM AuthPolicy after the Basic one in the list authPrefs to make it of less priority during the scheme selection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.