Return-Path: 
 <issues-return-83060-apmail-maven-issues-archive=maven.apache.org@maven.apache.org>
X-Original-To: apmail-maven-issues-archive@minotaur.apache.org
Delivered-To: apmail-maven-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5E4AEE737
	for <apmail-maven-issues-archive@minotaur.apache.org>;
 Fri, 11 Jan 2013 15:59:40 +0000 (UTC)
Received: (qmail 2253 invoked by uid 500); 11 Jan 2013 15:59:40 -0000
Delivered-To: apmail-maven-issues-archive@maven.apache.org
Received: (qmail 2216 invoked by uid 500); 11 Jan 2013 15:59:40 -0000
Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@maven.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@maven.apache.org>
List-Post: <mailto:issues@maven.apache.org>
List-Id: <issues.maven.apache.org>
Reply-To: dev@maven.apache.org
Delivered-To: mailing list issues@maven.apache.org
Received: (qmail 2208 invoked by uid 99); 11 Jan 2013 15:59:40 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 15:59:40 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [63.246.24.159] (HELO codehaus01.managed.contegix.com)
 (63.246.24.159)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 15:59:34 +0000
Received: from codehaus01 (localhost.localdomain [127.0.0.1])
	by codehaus01.managed.contegix.com (Postfix) with ESMTP id 4AD43B06AE
	for <issues@maven.apache.org>; Fri, 11 Jan 2013 09:59:13 -0600 (CST)
Date: Fri, 11 Jan 2013 09:59:13 -0600 (CST)
From: "Eddie Webb (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: 
 <385808801.31139.1357919953307.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
In-Reply-To: 
 <1678017411.30827.1357851733240.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
Subject: [jira] (SCM-710) Use of encrypted password in pom.xml confiuration
 is ignored
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 22cf62d5d84cf5bea94eb3b65e0ebd09
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://jira.codehaus.org/browse/SCM-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317189#comment-317189 ] 

Eddie Webb commented on SCM-710:
--------------------------------

I'll try the solution you mentioned and get back to you.  

The reason the latter is so valuable (and I really appreciate you taking a look!!) to us is that we use many different repos on that host, and leverage profiles to provide different teams an easy way to connect. (team A must specify -PteamA in order to get the proper credentials for their repo on the build server)  Using the hostname method bypasses the need for profiles and would require a globally authorized ID, and does not enforce the level of separation we prefer.
                
> Use of encrypted password in pom.xml confiuration is ignored
> ------------------------------------------------------------
>
>                 Key: SCM-710
>                 URL: https://jira.codehaus.org/browse/SCM-710
>             Project: Maven SCM
>          Issue Type: Bug
>            Reporter: Eddie Webb
>
> THe docs for this plugin say I can use encrypted passwords just like we do for the release plugin.
> It does not seem to support the same <project.scm.id>non-hostname-id</project.scm.id> that the release plugin does, so I included the username and encrypted password directory in the plugin config.
> {noformat}
> ...
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-scm-plugin</artifactId>
>         <version>1.8.1</version>
>         <configuration>
>           <username>username</username>
>           <password>{EncycptedStringGeneratedFromMvnPassword=}</password>
>         </configuration>
>       </plugin>
>     </plugins>
> ...
> {noformat}
> But the SCM fails with authentication issue, and the SVN logs determine that no user ID is sent.
> If I instead include the hostname as a server ID in settings.xml, or include these values on the command line, in both cases it invokes a 500 from the application server.
>  mvn scm:checkout -Pforge -Dusername=myuser -Dpassword={EncycptedStringGeneratedFromMvnPassword=}
> svn: Server sent unexpected return value (500 Internal Server Error) in response to OPTIONS request for https://my-svn
> This 500 can be duplicated in a browser by passing the un-encrypted string {foo=}.
> h3. summary
> regardless of where I place the encruypted password it is either ignored, or not decrypted before being sent to the webserver.  
> Can you please document an example of how to use the encrypted passwords, or support the same approach as the release plugin.
> http://jira.codehaus.org/browse/MRELEASE-420

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira