You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org> on 2007/05/11 05:21:15 UTC
[jira] Created: (QPID-486) .NET Client SASL implementation chooses
first matching mechanism instead of stronger
.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.
[jira] Updated: (QPID-486) .NET Client SASL implementation chooses
first matching mechanism instead of stronger
Posted by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Restrepo updated QPID-486:
--------------------------------
Attachment: QPID-486.diff
> .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
> Attachments: QPID-486.diff
>
>
> 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.
[jira] Resolved: (QPID-486) .NET Client SASL implementation chooses
first matching mechanism instead of stronger
Posted by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Restrepo resolved QPID-486.
---------------------------------
Resolution: Fixed
Fix Version/s: M2
Resolved in revision 537673
> .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
> Fix For: M2
>
> Attachments: QPID-486.diff
>
>
> 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.