[
https://issues.apache.org/jira/browse/SCM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962412#comment-17962412
]
ASF GitHub Bot commented on SCM-653:
------------------------------------
jira-importer opened a new issue, #860:
URL: https://github.com/apache/maven-scm/issues/860
**[Jeremie
BOUSQUET](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jbousque)**
opened
**[SCM-653](https://issues.apache.org/jira/browse/SCM-653?redirect=false)** and
commented
In SCM url format for integrity, credentials can be entered as
"login/password@hostname:port"
But if password contains '@' character (as 'toto@date'), then the integrity
provider interprets it as a separator (and tries to use "date@hostname" as
hostname).
I tried "toto\`@date`" but the same behaviour occurs.
---
**Affects:** 1.6
> '@' not supported in passwords in SCM urls
> ------------------------------------------
>
> Key: SCM-653
> URL: https://issues.apache.org/jira/browse/SCM-653
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-integrity
> Affects Versions: 1.6
> Environment: Java 1.6.0_11
> Maven 2.2.1
> MKS Source 2009
> Build: 8.10.0.5799
> Service Pack: 005-01
> Hotfixes: C041000005-019, C041000005-021
> Copyright 2001 - 2010 MKS Software Inc.; in Canada copyright owned by MKS
> Inc. All rights reserved.
> Reporter: Jeremie BOUSQUET
> Priority: Major
>
> In SCM url format for integrity, credentials can be entered as
> "login/password@hostname:port"
> But if password contains '@' character (as 'toto@date'), then the integrity
> provider interprets it as a separator (and tries to use "date@hostname" as
> hostname).
> I tried "toto\@date" but the same behaviour occurs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
