maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Moved: (WAGON-181) Support Kerberos authentication (at least for SshExternal)
Date Wed, 14 May 2008 07:30:30 GMT


Brett Porter moved WAGONSSH-35 to WAGON-181:

    Component/s:     (was: wagon-ssh)
            Key: WAGON-181  (was: WAGONSSH-35)
        Project: Maven Wagon  (was: wagon-ssh)

> Support Kerberos authentication (at least for SshExternal)
> ----------------------------------------------------------
>                 Key: WAGON-181
>                 URL:
>             Project: Maven Wagon
>          Issue Type: Wish
>          Components: wagon-ssh
>         Environment: Mac OS X 10.4
>            Reporter: Matthew Willis
> In Maven 1.x, when deploying an artifact to the repository via scp, leaving out the username
and password information let me deploy to an internal repository using the currently logged
in username and any Kerberos credentials that user may currently have.
> The wagon appears to only support password or key based ssh authentication. If I leave
all username/password information out of settings.xml, I am forced to enter a password (which
is echoed to the screen!). Simply pressing enter to dismiss the password dialog doesn't "fall
through" to using GSSAPI/Kerberos.
> From looking at the source, it appears that if a key is not specified, it defaults to
password auth. Could an option be added to allow using any existing GSSAPI/Kerberos credentials?
> Thanks

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message