Mailing-List: contact proton-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: proton@qpid.apache.org
Date: Fri, 4 Apr 2014 19:04:15 +0000 (UTC)
From: "Rafael H. Schloming (JIRA)" <jira@apache.org>
To: proton@qpid.apache.org
Message-ID: <JIRA.12706316.1396478028637.65956.1396638255908@arcas>
In-Reply-To: <JIRA.12706316.1396478028637@arcas>
References: <JIRA.12706316.1396478028637@arcas>
Subject: [jira] [Resolved] (PROTON-553) Proton-C does not URLdecode password
 before doing SASL-PLAIN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/PROTON-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rafael H. Schloming resolved PROTON-553.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.7
         Assignee: Rafael H. Schloming

> Proton-C does not URLdecode password before doing SASL-PLAIN
> ------------------------------------------------------------
>
>                 Key: PROTON-553
>                 URL: https://issues.apache.org/jira/browse/PROTON-553
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.7
>            Reporter: James Birdsall
>            Assignee: Rafael H. Schloming
>             Fix For: 0.7
>
>         Attachments: sasl.c
>
>
> This is a serious issue using Proton-C against ServiceBus because our passwords are base64-encoded keys and frequently contain '/'. Previous versions of Proton-C didn't care about technically illegal forward slashes in the URL, but 0.7 sure does. URL encoding the password gets around that, but then the encoded password is presented to our broker and is rejected. Since Proton is the one dealing with a URL and enforcing URL rules, it should do the decoding before passing the pieces on to other layers.


--
This message was sent by Atlassian JIRA
(v6.2#6252)