[SCM-832] maven-scm-provider-jgit should support SSH public key auth

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.4
• Fix Version/s: 1.11.2
• Component/s: maven-scm-provider-gitexe, maven-scm-provider-jgit
• Assignee: Olivier Lamy
• Reporter: Martin Kutter
• Created: 14/Jun/16 19:29
• Updated: 14/Dec/18 04:14
• Resolved: 14/Dec/18 04:14

Description

The current mvn-scm-provider-jgit implementation does not support the explicit use of public key auth. The underlying implementation implicitly uses ~/id_rsa or ~/id_dsa if present (and not protected by a passphrase).
For most Git repositories (Github, Gitlab, ...), public key authentication is mandatory for ssh access.
This forces users to either use https, or to rely on a unprotected private key file.

maven-scm-provider-jgit should support the privateKey and passphrase attributes available in server entries in maven settings.xml for ssh URLs

Issue Links

• links to: GitHub Pull Request #50
• links to: GitHub Pull Request #50