qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomas Restrepo (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Created: (QPID-486) .NET Client SASL implementation chooses first matching mechanism instead of stronger
Date Fri, 11 May 2007 03:21:15 GMT
.NET Client SASL implementation chooses first matching mechanism instead of stronger
------------------------------------------------------------------------------------

                 Key: QPID-486
                 URL: https://issues.apache.org/jira/browse/QPID-486
             Project: Qpid
          Issue Type: Bug
          Components: Dot Net Client
    Affects Versions: M2
            Reporter: Tomas Restrepo
         Assigned To: Tomas Restrepo
            Priority: Minor


The SASL implementation in the .NET client currently chooses the first matching mechanism
found in the mechanism list returned by the broker during connection start. However, it should
try to pick the "stronger" mechanism if possible.

Because of this, currently the .NET client will usually choose PLAIN authentication even if
the broker reports it supports CRAM-MD5.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message