Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-15653

Remote docker repositories should support the access_token response field

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 5.8.3
    • Fix Version/s: 6.0.0
    • Component/s: Docker, Remote Repository
    • Labels:
      None

      Description

      The docker spec says the client is compatible with both the "token" and the "access_token" fields - Remote repos on Artifactory should be compatible with the access_token field as well when bearer auth is initiated (currently only the "token" response field is supported):

      "For compatibility with OAuth 2.0, we will also accept token under the name access_token. At least one of these fields must be specified, but both may also appear (for compatibility with older clients). When both are specified, they should be equivalent; if they differ the client's choice is undefined."

      Taken from https://docs.docker.com/registry/spec/auth/token/#token-response-fields

        Attachments

          Activity

            People

            • Assignee:
              uriahl Uriah Levy
              Reporter:
              uriahl Uriah Levy
              Assigned QA:
              Tamir Hadad
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: