Using Nexus 2.3.0-04 OSS protected by authentication to host yum repositories

[Natalia Usmanova]

Hi!

This plugin is exactly what we need, and it could solve a lot of problems for us. However, currently it has a blocking issue, which makes it impossible for us to use it effectively.

We need our Nexus repositories, including the yum repositories to be protected by authentication. Deploying to a yum repository hosted in Nexus via maven works fine. Command "yum list" works fine too, and finds the correct rpms. However, "yum install" fails with 401 HTTP error. It seems that while "yum list' command carries over the username and password specified in our yum config file, "yum install" command looses it when it tries to actually download the file. This behavior is exactly the same as described in this entry: http://code.google.com/p/nexus-yum-plugin/issues/detail?id=17  We are running yum commands on Centos 6.3 machines (yum 3.2.29).

Questions:

1. Does this problem exist in the latest version of Nexus Enterprise?

2. If yes, is there any known work around that could make "yum install" use given username and password?

2. If not, are there any plans to fix the issue 17 specified above?

Thank you,

Natalia.

[Herold, Sebastian]

Hi,

the problem still exists, because Nexus generates Yum metadata with absolute urls to the RPMs. But these absolute urls doesn't contain the credentials given by your .repo file. Atm there is no workaround, but hopefully I'll fix that issue next week. Then, its on Sonatype to build a new maintenance release. 

Regards,

Sebastian

[Natalia Usmanova]

Thank you for such a quick reply!  It would be extremely helpful if this issue was fixed. I am willing to get the code, build and test it as soon as it's ready. We are considering upgrading to the Enterprise edition, and knowing that we could use Nexus to host yum repos will definitely help us with this decision.

Regards,

Natalia.

[Natalia Usmanova]

I saw that the related issue was fixed in GitHub, so I downloaded the latest code, built and tested it. Everything worked as expected, and I was able to install rpms from the repo protected by authentication. Thank you very much!!!