[jira] [Closed] (SCM-832) maven-scm-provider-jgit should support SSH public key auth

["Olivier Lamy (*$^¨%`£ JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SCM-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy (*$^¨%`£) closed SCM-832.
--------------------------------------
    Resolution: Fixed

[~mkutter] thanks for your contribution!

> 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
>            Assignee: Olivier Lamy (*$^¨%`£)
>            Priority: Major
>             Fix For: 1.11.2
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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
(v7.6.3#76005)