Project

Profile

Help

Story #6315

closed

As a user I can mirror from a registry with a pull secret

Added by ipanova@redhat.com about 4 years ago. Updated almost 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Backlog, Documentation
Sprint:
Quarter:

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.


Related issues

Copied from Docker Support - Story #6311: As a user I can mirror from a registry with a secret pullCLOSED - WONTFIXipanova@redhat.com

Actions

Also available in: Atom PDF