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

Lorenz Quack updated QPID-7964:
-------------------------------
    Description: 
Currently the Qpid Client for Java for AMQP 0-x encodes the characters "=" and 
"," in passwords when using the SCRAM SASL mechanism.
This is incorrect. [The spec|https://tools.ietf.org/html/rfc5802] requires 
encoding of those characters for the username. Not for the password.

This was reported on the [user mailing 
list|http://mail-archives.apache.org/mod_mbox/qpid-users/201710.mbox/%3C1507290028737-0.post%40n2.nabble.com%3E]

  was:
Currently the Qpid Client for Java for AMQP 0-x encodes the characters "=" and 
"," in passwords when using the SCRAM SASL mechanism.
This is incorrect. [The spec|https://tools.ietf.org/html/rfc5802] requires 
encoding of those characters for the username. Not for the password.




> [Java Client, AMQP 0-x] SCRAM AuthenticationProvider incorrectly encodes "=" 
> and "," for passwords
> --------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7964
>                 URL: https://issues.apache.org/jira/browse/QPID-7964
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Lorenz Quack
>
> Currently the Qpid Client for Java for AMQP 0-x encodes the characters "=" 
> and "," in passwords when using the SCRAM SASL mechanism.
> This is incorrect. [The spec|https://tools.ietf.org/html/rfc5802] requires 
> encoding of those characters for the username. Not for the password.
> This was reported on the [user mailing 
> list|http://mail-archives.apache.org/mod_mbox/qpid-users/201710.mbox/%3C1507290028737-0.post%40n2.nabble.com%3E]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to