Project

Profile

Help

Story #1144

closed

As a user, I can sync from a v2 registry that requires RFC7235 authorization headers

Added by rbarlow about 9 years ago. Updated over 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Target Release - Docker:
2.0.0
Groomed:
No
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Quarter:

Description

The Docker registry may return a 401 Unauthorized response on some requests. If this happens, Pulp needs to be able to support RFC7235 authorization headers in order to continue.

Deliverables:

  • Pulp can sync against a registry that requires authorization headers
  • pulp-admin support
  • Tests
  • Documentation

[0] https://github.com/docker/distribution/blob/release/2.0/docs/spec/api.md#on-failure-unauthorized
[1] http://tools.ietf.org/html/rfc7235


Related issues

Related to Nectar - Issue #1567: Nectar threaded downloader's event listener cannot issue another requestCLOSED - CURRENTRELEASEamacdona@redhat.comActions
Related to Docker Support - Issue #1598: clarify docs that index.docker.io only supported for v1CLOSED - CURRENTRELEASEipanova@redhat.comActions
Blocked by Docker Support - Story #968: As a user, I can sync from a v2 registryCLOSED - CURRENTRELEASErbarlow

Actions
Blocks Docker Support - Task #1048: Tracker for Docker v2 API and Manifest workCLOSED - CURRENTRELEASErbarlow

Actions
Blocks Docker Support - Issue #1404: Sync from un-namespaced V2 repository failsCLOSED - CURRENTRELEASEamacdona@redhat.comActions
Blocks Docker Support - Story #1454: As a user, I can sync v2 content from docker hubCLOSED - CURRENTRELEASEamacdona@redhat.com

Actions

Also available in: Atom PDF