Story #6315
closed
As a user I can mirror from a registry with a pull secret
Status:
CLOSED - CURRENTRELEASE
Tags:
Backlog, Documentation
Description
Motivation¶
Pulp registry can accept basic auth credentials only in plain text. Nowadays these credentials very often are based64 encoded and stored in the auth.json file. Pulp Registry is not able to use already encoded credentials, as a result it produces bad user experience where users are forced to decode the credentials manually and provide them to Pulp Registry.
Solution¶
Pull secret is a base64 encoded username+password. It can contain credentials to multiple registries.
Add an option called pull-secret
which will accept the absolute path to the pull secret file info in the json format. Pulp will parse it and extract the auth
part which will be used in the Basic auth headers and sent to the external registry.
Example of a pull secret can be obtained here https://cloud.redhat.com/openshift/install/pre-release or perform 'podman login' and look for the created auth file http://docs.podman.io/en/latest/markdown/podman-login.1.html
Note¶
Make sure that 'pull-secret' and 'username and password' are mutually exclusive options.
- Copied from Story #6311: As a user I can mirror from a registry with a secret pull added
- Groomed changed from No to Yes
- Sprint set to Sprint 69
- Sprint changed from Sprint 69 to Sprint 70
- Sprint changed from Sprint 70 to Sprint 71
- Sprint deleted (
Sprint 71)
- Description updated (diff)
- Description updated (diff)
- Subject changed from As a user I can mirror from a registry with a secret pull to As a user I can mirror from a registry with a pull secret
- Description updated (diff)
- Description updated (diff)
- Status changed from NEW to ASSIGNED
- Assignee set to lmjachky
- Tags Documentation added
- Tags deleted (
Backlog)
After today's meeting we have decided to add documentation on how to handle situation when credentials are stored in the auth file.
The original proposal would not work in the case when the user would not have access to the filesystem. Also it would not make sense to provide in the Remote access to the credentials of all the registries stored in that file.
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Sprint/Milestone set to 1.4.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
Add a new section about using pull secrets
closes #6315