ArgoCD Support for Custom Authentication Headers for Repository Access

[kirkpabk]

Depending on the host configurations and perhaps hardening, inline PATs (or usr:pwd in the url) would no longer work. Instead, such credentials must be passed as a Base64-encoded basic authentication header such as:

Authorization: Basic Om9uNWt0bGfakeVkcXlvbaTZsaXFpYzJhNjfakeZsbm5zcGJuaHFtcnlvdWo3bmEzMnNu9GE=

which would have the Base64 representation of ":129uNt0GfakeVkXlvbTZsaXFpYzJhjfakeZsb" (empty user name, : and PAT value) or a username:password.

Illustration for clarity

$token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($PAT)"))
$header = "Authorization: Basic $token"

In GIT, for instance, we can get around the inline PAT by passing an http.extraheader= to the --config-env parameter.

I think it would help with integrations if ArgoCD provided this sort of usecase similar to the GIT extra header within the Connect Repository dialog. As it stands now, we can't connect, so we'll need to move onto another product for our platform.