[
https://issues.apache.org/jira/browse/QPID-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602729#action_12602729
]
Robert Greig commented on QPID-1058:
------------------------------------
How about this - instead of sending over the hashed bytes as UTF-8 send over
the hashed bytes as a hex string [as UTF-8]? Then we just have to be able to
handle A-F and 0-9 which should just about be possible :-)
I take it that the hashing is our own scheme so we are free to turn that into a
hex string if we want?
> Add support for CRAM-MD5-HASHED as used by Java Broker
> ------------------------------------------------------
>
> Key: QPID-1058
> URL: https://issues.apache.org/jira/browse/QPID-1058
> Project: Qpid
> Issue Type: New Feature
> Components: Dot Net Client
> Affects Versions: M2, M2.1
> Reporter: Martin Ritchie
> Fix For: M3
>
>
> Summary:
> As shown on the Qpid Interoperability page the .Net does not currently
> support the CRAM-MD5-HASHED SASL mechanism offered by the Java broker.
> http://cwiki.apache.org/confluence/display/qpid/Qpid+Interoperability+Documentation
> For the .Net client to interoperate with the Java broker using the Base64
> encoded MD5Hashed password file the .Net client needs to support this
> mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
