You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Kutter (JIRA)" <ji...@apache.org> on 2016/06/14 19:29:56 UTC
[jira] [Created] (SCM-832) maven-scm-provider-jgit should support
SSH public key auth
Martin Kutter created SCM-832:
---------------------------------
Summary: maven-scm-provider-jgit should support SSH public key auth
Key: SCM-832
URL: https://issues.apache.org/jira/browse/SCM-832
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-provider-gitexe, maven-scm-provider-jgit
Affects Versions: 1.9.4
Reporter: Martin Kutter
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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)