You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Gilles Sadowski <gi...@harfang.homelinux.org> on 2009/03/30 00:33:22 UTC
Problem with authentication
Hello.
I try to copy (i.e. "install") files from a password-protected "ibiblio"
repository to a "filesystem" repository. But I'm stuck with a 401 response.
Below is the relevant part of the output using the '-d' switch.
---CUT---
[...]
credentials added: gaia.esac.esa.int cudev/**********
[...]
[ivy:install] == resolving dependencies apache#ivy-install;1.0->gaia.cu1.tools#GaiaTools;6.0 [default->*]
[ivy:install] loadData of gaia.cu1.tools#GaiaTools;6.0 of rootConf=default
[ivy:install] using gaia to resolve gaia.cu1.tools#GaiaTools;6.0
[ivy:install] no ivy file in cache for gaia.cu1.tools#GaiaTools;6.0: tried /home/dummy/ivy/cache/gaia.cu1.tools/GaiaTools/ivy-6.0.xml
[ivy:install] trying http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.pom
[ivy:install] tried http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.pom
[ivy:install] authentication: k='Sonatype Nexus Repository Manager@gaia.esac.esa.int' c='null'
[ivy:install] HTTP response status: 401 url=http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.pom
[ivy:install] CLIENT ERROR: Unauthorized url=http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.pom
[ivy:install] gaia: resource not reachable for gaia/cu1/tools#GaiaTools;6.0: res=http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.pom
[ivy:install] trying http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.jar
[ivy:install] tried http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.jar
[ivy:install] authentication: k='Sonatype Nexus Repository Manager@gaia.esac.esa.int' c='null'
[ivy:install] HTTP response status: 401 url=http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.jar
[ivy:install] CLIENT ERROR: Unauthorized url=http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.jar
[ivy:install] gaia: resource not reachable for gaia/cu1/tools#GaiaTools;6.0: res=http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.jar
[ivy:install] gaia: no ivy file nor artifact found for gaia.cu1.tools#GaiaTools;6.0
[ivy:install] WARN: module not found: gaia.cu1.tools#GaiaTools;6.0
[ivy:install] WARN: ==== gaia: tried
[ivy:install] WARN: http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.pom
[ivy:install] WARN: -- artifact gaia.cu1.tools#GaiaTools;6.0!GaiaTools.jar:
[ivy:install] WARN: http://gaia.esac.esa.int/nexus/content/repositories/gaiacentral/gaia/cu1/tools/GaiaTools/6.0/GaiaTools-6.0.jar
[ivy:install] Nbr of module to sort : 0
[...]
---CUT---
My ivy "settings" file contains a <credentials> tag, and the info there is
correct because I can connect to the repository with a web browser using the
same username and password.
In particular, in the above log excerpt, I can't understand the lines saying:
authentication: k='Sonatype Nexus Repository Manager@gaia.esac.esa.int' c='null'
What is 'k' and what is 'c'?
Why doesn't ivy use the username and password?
Thanks,
Gilles
Re: Problem with authentication [SOLVED]
Posted by Gilles Sadowski <gi...@harfang.homelinux.org>.
Hi.
Replying to my own question:
> In particular, in the above log excerpt, I can't understand the lines saying:
>
> authentication: k='Sonatype Nexus Repository Manager@gaia.esac.esa.int' c='null'
This was indeed the problem. The "Sonatype Nexus Repository Manager" string
indicated above *must* be set as the "realm" attribute in <credentials>.
I think that it would be worth mentioning such pitfalls in the
documentation...
Gilles