This page documents the various interoperable features of the Qpid clients.
This table list the various SASL mechanisms that each component supports. The version listed shows when this functionality was added to the product.
Table 1.14. SASL Mechanism Support
|C++ Broker||M3[Section 220.127.116.11, “ Standard Mechanisms ”]||M3[Section 18.104.22.168, “ Standard Mechanisms ”,Section 22.214.171.124, “ Standard Mechanisms ”]||M3[Section 126.96.36.199, “ Standard Mechanisms ”,Section 188.8.131.52, “ Standard Mechanisms ”]||M1|
|C++ Client||M3[Section 184.108.40.206, “ Standard Mechanisms ”]||M1|
2: C++ Broker uses Cyrus SASL which supports CRAM-MD5 and GSSAPI but these have not been tested yet
There have been some custom mechanisms added to our implementations.
Table 1.15. SASL Custom Mechanisms
The Java SASL implementations require that you have the password of the user to validate the incoming request. This then means that the user's password must be stored on disk. For this to be secure either the broker must encrypt the password file or the need for the password being stored must be removed.
The CRAM-MD5-HASHED SASL plugin removes the need for the plain text password to be stored on disk. The mechanism defers all functionality to the build in CRAM-MD5 module the only change is on the client side where it generates the hash of the password and uses that value as the password. This means that the Java Broker only need store the password hash on the file system. While a one way hash is not very secure compared to other forms of encryption in environments where the having the password in plain text is unacceptable this will provide and additional layer to protect the password. In particular this offers some protection where the same password may be shared amongst many systems. It offers no real extra protection against attacks on the broker (the secret is now the hash rather than the password).