Support OAuth-based Git Authentication via Git CLI

Manta currently supports pulling files from Git repositories for scanning purposes. It uses the JGit library to establish Git connections.

However, modern Git providers are increasingly moving away from static credentials (username/password or long-lived access tokens) in favor of short-lived, OAuth-based authentication mechanisms. This shift is already standard across major platforms such as GitHub, GitLab, and Azure DevOps.

At present, Manta does not support OAuth-based authentication for Git. This limitation stems in part from differences in OAuth implementations across Git providers—there is no single standardized flow that works universally across GitHub, GitLab, and Azure DevOps.

That said, these platforms commonly support Git credential helper plugins that abstract away these differences and enable OAuth authentication. Examples include:

• https://github.com/hickford/git-credential-oauth 
• https://github.com/git-ecosystem/git-credential-manager 

Additionally, the Git CLI allows users to leverage the above or even custom credential helpers to support a wide range of authentication mechanisms, including OAuth.

The core limitation is that Manta relies on JGit rather than the native Git CLI. JGit does not support these credential helper plugins, and therefore cannot leverage OAuth-based authentication through them.

Requested Enhancement: Provide an option in Manta to use the native Git CLI instead of JGit for repository access. This would allow customers who require OAuth-based authentication to take advantage of existing Git credential helpers and custom authentication plugins.

This capability would:

• Enable compatibility with modern authentication standards (OAuth)
• Reduce the need for custom provider-specific implementations within Manta
• Improve integration with enterprise security policies that mandate short-lived credentials