Skip to content

Added unavailable basic_auth for authorization for maven packages

What does this MR do and why?

The problem is that the GitLab Package Registry when using a personal access token does not support basic HTTP auth for Maven and Gradle. It does for deploy tokens, but the registry will return a 400 response when it should return a 404, which can mislead Developers.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

General setup for maven packages publishing Maven packages in the Package Registry

MR acceptance checklist

Must worked

  • curl -u "Deploy-Token:XXXX" <my_package_url>
  • curl -u "<deploy_token_username>:XXXX" <my_package_url>
  • curl -u "foo:XXXX" <my_package_url>

and

  • wget --user=Deploy-Token --password=XXX <my_package_url>
  • wget --user= --password=XXX <my_package_url>

Related to #277385 (closed)

Edited by Vitaliy Holovko

Merge request reports