[
https://issues.apache.org/jira/browse/QPID-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466495
]
Tomas Restrepo commented on QPID-291:
-------------------------------------
Attached new patch (QPID-291-2.diff) that replaces the previous attempts. This
one clears up a bunch of FXCOP warnings and also implements configuration for
both the Qpid.Sasl library as well as the CallbackHandlerRegistry in
Qpid.Client. This means you can now configure new SASL mechanisms as well as
new IAMQCallbackHandler implementations for authentication using the app.config
file.
Examples of both are included in the App.Config files for the Qpid.Sasl.Tests
and Qpid.Client.Tests projects.
> Support SASL authentication in .NET client
> ------------------------------------------
>
> Key: QPID-291
> URL: https://issues.apache.org/jira/browse/QPID-291
> Project: Qpid
> Issue Type: New Feature
> Components: Dot Net Client
> Affects Versions: M2
> Environment: .NET 1.1 and .NET 2.0
> Reporter: Tomas Restrepo
> Priority: Minor
> Attachments: DotnetAuthentication.diff, QPID-291-2.diff, QPID-291.diff
>
>
> The .NET client only has a hardcoded implementation of the PLAIN
> authentication mechanism. It lacks a real SASL implementation on the client
> side, and so has no way to support other authentication mechanisms. Right
> now, the Java broker supports both PLAIN and CRAM-MD5 authentication, so at
> least those two should be supported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
