Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-22134

add support to Maven proxy repository for gitlab private maven repository http header token authentication

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.24.0
    • Fix Version/s: None
    • Component/s: Maven
    • Labels:
    • Notability:
      4

      Description

      Gitlab repository only provides authentification using custom HTTP Headers, for example Private-Token

      https://docs.gitlab.com/ee/user/packages/maven_repository/#authenticate-to-the-package-registry-with-maven
       

      Adding "Custom fragment to append to "User-Agent" header in HTTP requests." not works

      Gitlab documentation states:

      If a project is private or you want to upload Maven artifacts to GitLab, credentials will need to be provided for authorization too. Support is available for personal access tokensCI job tokens, and deploy tokens only. Regular username/password credentials do not work.

       

      Expected

      We mainly want to have special HTTP header authentication working with gitlab remotes.

      Though a possible impl. would be to allow a new proxy repository option to specify adding custom outbound HTTP headers and values for every method of request - though that might be overkill on further analysis, depending how/if gitlab sends auth challenges.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jflefebvre JF Lefebvre
              Last Updated By:
              Dawid Sawa Dawid Sawa
              Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Date of First Response:

                  tigCommentSecurity.panel-title