GitLab.com hostRule token not applied for private Maven registry (401 Unauthorized) #39534
Unanswered
nuwan-samarasinghe
asked this question in
Request Help
Replies: 1 comment
-
|
We actually seem to have the same issue, but for composer (PHP). The PATs work using curl, but renovate doesn't seem to handle correctly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate
Which platform you running Renovate on?
GitLab (.com or self-hosted)
Which version of Renovate are you using?
42.19.7
Please tell us more about your question or problem
Renovate fails to authenticate against a private GitLab Maven repository even though a matching hostRule is configured with a valid GitLab personal access token.
The same token works when tested manually (Postman / curl).
Renovate always returns 401 Unauthorized when trying to fetch Maven metadata from GitLab’s package registry endpoint.
Maven repository URL Renovate needs to access
https://gitlab.com/api/v4/projects/<project_id>/packages/mavenManual request using Postman
this gives a success
personal access token as api and all other read access testing purpose I added
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions