Skip to content

Implement token authentication (Docker Registry HTTP API V2) #2442

Open
@KhalefAhmed

Description

@KhalefAhmed

The docker-java client does not yet support the token authentication flow defined by the official specification at https://distribution.github.io/distribution/spec/auth/token/

Authentication Flow (text):

  1. Client sends initial request to registry without any authentication header.
  2. Registry responds with 401 Unauthorized and a WWW-Authenticate header specifying the token endpoint.
  3. Client issues a GET request to the token endpoint (/token) with service and scope query parameters.
  4. Auth server returns JSON containing token, expires_in, and issued_at.
  5. Client retries the registry request, including Authorization: Bearer .
  6. Registry responds with 200 OK and the requested payload.

I would be willing to contribute this improvement with guidance from the docker-java community

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy