[
https://issues.apache.org/jira/browse/IVY-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053392#comment-16053392
]
jaikiran pai commented on IVY-1557:
-----------------------------------
[~sclarke], we have started publishing nightly builds of Ivy. If you are
interested, you can give it a try containing this fix. The next build (around 7
hours from now) of the nightly job[1] should have this fix.
[1]
https://builds.apache.org/view/A/view/Ant/job/Ivy-NightlyDistribution/lastSuccessfulBuild/
> Request info lost when IvyAuthenticator delegates to wrapped authenticator
> --------------------------------------------------------------------------
>
> Key: IVY-1557
> URL: https://issues.apache.org/jira/browse/IVY-1557
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Shane Clarke
> Assignee: jaikiran pai
> Fix For: master
>
>
> Hit this in an environment with multiple authenticators.
> IvyAuthenticator gets set as default during an ivy resolve wrapping the
> previous authenticator.
> Any subsequent password authentication request using
> Authenticator.requestPasswordAuthentication(String host, InetAddress addr,
> int port, String protocol, String prompt, String scheme, URL url,
> Authenticator.RequestorType reqType) that the IvyAuthenticator can't handle
> will be delegated to the 'original' wrapped authenticator.
> But the requestingURL and requestingAuthType fields in the original request
> will be lost.
> The IvyAuthenticator is delegating using
> Authenticator.requestPasswordAuthentication(String host, InetAddress addr,
> int port, String protocol, String prompt, String scheme)
> Which resets all fields to null and sets them to the method arguments losing
> the two fields.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
