[
https://issues.apache.org/jira/browse/QPIDJMS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230166#comment-15230166
]
Timothy Bish commented on QPIDJMS-169:
--------------------------------------
Thanks Robbie. I had re-read the SASL PLAIN RFC last night just to be sure
that I'd read the requirements right and as Robbie pointed out it is not
mandated in the RFC but the UTF8 bit is so fixing that was my main priority for
this JIRA. I hadn't had time to chase down other implementations to see if any
did a prep for plain but it seems Robbie did some legwork there.
For now I think this change is correct and at least gets us in line with the
basic requirements. We of course are happy to have contributions so if someone
want to jump on the SaslPrep implementation that'd be a nice add.
> SASL Plain Mechanism should be enforcing UTF-8 encoding
> -------------------------------------------------------
>
> Key: QPIDJMS-169
> URL: https://issues.apache.org/jira/browse/QPIDJMS-169
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.8.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 0.9.0
>
>
> When encoding the user / pass in the SASL plain mechanism we aren't enforcing
> UTF-8 encoding which is the required encoding.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
