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/01/14 15:46:27 UTC
[jira] Created: (QPID-291) Support SASL authentication in .NET
client
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
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
[jira] Commented: (QPID-291) Support SASL authentication in .NET
client
Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468229 ]
Rupert Smith commented on QPID-291:
-----------------------------------
I applied this patch and it looks good to me.
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-291) Support SASL authentication in .NET
client
Posted by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Restrepo updated QPID-291:
--------------------------------
Attachment: DotnetAuthentication.diff
> 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
>
>
> 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
[jira] Resolved: (QPID-291) Support SASL authentication in .NET
client
Posted by "Robert Greig (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Greig resolved QPID-291.
-------------------------------
Resolution: Fixed
Fix Version/s: M2
Patch applied svn revision 501001
> 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
> Fix For: M2
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-291) Support SASL authentication in .NET
client
Posted by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>.
[ 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
[jira] Updated: (QPID-291) Support SASL authentication in .NET
client
Posted by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Restrepo updated QPID-291:
--------------------------------
Attachment: QPID-291-2.diff
> 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
[jira] Commented: (QPID-291) Support SASL authentication in .NET
client
Posted by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465196 ]
Tomas Restrepo commented on QPID-291:
-------------------------------------
Attached a new patch that replaces the original one. This includes various fixes including one that caused the ConnectionCloseOK method to not be sent to the server during an authentication failure.
> 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.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
[jira] Updated: (QPID-291) Support SASL authentication in .NET
client
Posted by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Restrepo updated QPID-291:
--------------------------------
Attachment: QPID-291.diff
> 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.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