[jira] [Updated] (CLOUDSTACK-6053) While adding smb as primary or secondary the password should be uri encoded
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-6053: -- Labels: S1 (was: ) 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 Labels: S1 Fix For: 4.4.0 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.2#6252)
[jira] [Updated] (CLOUDSTACK-6053) While adding smb as primary or secondary the password should be uri encoded
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-6053: -- Fix Version/s: 4.3.0 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 Fix For: 4.3.0 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)
