James Mansion wrote:
The WindowsSasl implementation doesn't do anything Windows-ish. Why isn't this basic implementation the default if CyrusSasl is not available?
There is code in the ConnectionHandler that is intended to cover the case where a specific SaslFactory is not available that does broadly the same thing.
Is it intended that a Windows security token could be passed? This makes sense for Windows deployments, but might also be workable for non-Windows brokers that have access to a domain controller. If you can support single signon for Windows client applications, there will be general rejoicing.
Cyrus SASL does claim support for NTLM, though I have not tested that. I have tested GSSAPI.
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
