Gitlab repository only provides authentification using custom HTTP Headers, for example Private-Token
Adding "Custom fragment to append to "User-Agent" header in HTTP requests." not works
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 tokens, CI job tokens, and deploy tokens only. Regular username/password credentials do not work.
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.