Nexus 3 - proxy repository auth against internal docker registry

755 views
Skip to first unread message

Daniel Perez

unread,
Jan 12, 2016, 2:45:27 PM1/12/16
to Nexus Users
I have set up a docker proxy repo against an internal docker registry being hosted in our company. This proxy has it's own authentication realm (tied to LDAP) when you want to push/pull. The authentication methods differ compared to my nexus3 instance (our nexus uses company email as username and internal docker registry uses unixid, same password though)

What would be the proper way to pass the right credentials when doing docker login to authenticate against the proxied docker registry? 

our nexus url = nexusdev-3.mycompany.com:18501 (port I used for this proxy registry)

If I do docker login some-registry.mycompany.com and do docker pulls/pushes, it works

if i try doing

docker login nexusdev.mycompany.com:18501 and use the internal registry credentials, I cannot login. I have to use my nexus credentials to log in.

- Daniel

Peter Lynch

unread,
Jan 18, 2016, 4:59:06 PM1/18/16
to Daniel Perez, Nexus Users
Hi Daniel,

Requiring your Nexus credentials would be Nexus working as designed. Nexus does not forward your credentials to the remote proxied repository for authentication.

It sounds like you need to configure Nexus to use the same LDAP server that your internal registry is using. If you do this, the you should be able to login to Nexus ( and access the Nexus repository ) using LDAP credentials.


 
- Daniel

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/90d52dbc-a585-41f8-b617-c669459dc645%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

Reply all
Reply to author
Forward
0 new messages