[
https://issues.apache.org/jira/browse/QPIDJMS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230102#comment-15230102
]
Robbie Gemmell commented on QPIDJMS-169:
----------------------------------------
The newer RFCs seem to recommend saslprep rather than require it (probably
since the earlier RFCs defining the mech are older than sasl-prep, except the
SCRAM ones, which perhaps have more need for it since they use a more
structured content), with not doing prep mentioned as one approach during
discussion that different components can behave differently.
The JVMs built in PLAIN sasl client code doesnt seem to do any prep and just
encodes the input directly as UTF8, which appears to be what our other bits are
also doing currently. Regardless, this change really just ensures the existing
behaviour is fixed rather than floating about if a non-UTF8 default is in
place, so I think it seems reasonable. Any further changes seem like something
additional JIRAs would handle, and would likely need to be coordinated across
all the components as you say.
> 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: [email protected]
For additional commands, e-mail: [email protected]
