[jira] Commented: (QPID-1058) Add support for CRAM-MD5-HASHED as used by Java Broker

["Aidan Skinner (JIRA)" <qp...@incubator.apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602698#action_12602698 ] 

Aidan Skinner commented on QPID-1058:
-------------------------------------

Wow, ok, lots of pain. Java's penchant for UTF-8 encoding all and sundry totally breaks this, as it and .Net have a different idea of what you do with characters in the undefined range.

I implemented an alternate DIGEST-MD5-HASHED mechanism which I thought would solve the problem as it has a property to twiddle that controls the character encoding, but that's been removed in JDK6. 

Current plan would be to implement our own DIGEST-MD5 provider, rather than wrapping the system one and not munging the password, but I've been unable to find an ASL licensced implementation to repurpouse. Harmony doesn't seem to have it, although it claims 100% complete SASL class coverage... *shrug*



> 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.