cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-6053) While adding smb as primary or secondary the password should be uri encoded
Date Fri, 07 Feb 2014 12:19:19 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894451#comment-13894451
] 

ASF subversion and git services commented on CLOUDSTACK-6053:
-------------------------------------------------------------

Commit f0b861fedeea9e752665a42231f910112c5b8b46 in branch refs/heads/4.3-forward from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f0b861f ]

CLOUDSTACK-6053: While adding a primary or secondary of type smb the password wasn't
encoded. This cause createStoragePool or addImageStore command to fail if special
characters were present. Updated the code to pass user, password and domain as part
of details while adding primary or secondary. Also made changes on server side to
handle it.


> While adding smb as primary or secondary the password should be uri encoded
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6053
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6053
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.3.0
>            Reporter: Devdeep Singh
>            Assignee: Devdeep Singh
>
> When a smb share is added as a primary or secondary the user, password and domain are
passed in the url. If the password has special characters (like &) added the share fails
as the server isn't able to parse the uri.
> User, password and details should be passed as details parameters in the api   and the
server side should be updated to understand it.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message