This repository has been archived by the owner on Mar 31, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 493
MavenPomAuthSupplier doesn't decrypt passwords #179
Comments
support since V1.4.3 |
can someone confirm ? for me it doesn't work |
doesn't work for me in 1.4.3 Edit: I traced what happens - password is decrypted in com.spotify.plugin.dockerfile.MavenRegistryAuthSupplier#authFor(String imageName) on push, but on build you might need to download base image from secured docker-registry, in this case password is not decrypted and passed as is, see dockerfile-maven/plugin/src/main/java/com/spotify/plugin/dockerfile/MavenRegistryAuthSupplier.java Line 100 in 19f1f42
|
andreysaksonov
added a commit
to andreysaksonov/dockerfile-maven
that referenced
this issue
Jul 25, 2018
Sorry I opened a duplicate #204 |
davidxia
added a commit
that referenced
this issue
Aug 8, 2018
gh-179 fix password decryption on docker pull
This problem has been addressed by the 1.4.4 release and should be closed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
BUG REPORT:
Description
When attempting to pull from a registry during the build process, if maven authentication is enabled and an encrypted password is used, the process by which the password is retrieved doesn't decrypt the password, instead sending it as-is, subsequently causing an authorisation failure.
How to reproduce
What do you expect
The pull should start without any errors.
What happened instead
An authorisation error was produced, citing bad credentials used in the connection.
Software:
docker version
:Full backtrace
The text was updated successfully, but these errors were encountered: