[DISPATCH-958] Lacking documentation on authorization, authentication and SSL.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.1
• Component/s: Documentation
• Assignee: Ben Hardesty
• Reporter: Alan Conway
• Created: 06/Apr/18 14:55
• Updated: 02/Apr/21 10:21

Description

All the configuration attributes related to security are well documented, but it's not at all easy to figure out which attributes you need to set in order to create basic secure configurations.

Suggest adding a section to chapter 3 of the dispatch book showing how to configure:

• Entirely insecure router for trusted network/development work
• Simple SSL
• SASL PLAIN+SSL for simple secure authentication.
• allow-insecure+PLAIN (no SSL) for simple auth in a trusted network/dev env.
• at least one of SASL's distributed auth mechansims (Kerberos, LDAP)

We don't want to document everything about SASL, but we do need to show all the ways it can be used from dispatch  - at least enough so people can look at e.g. an LDAP dispatch example and then use SASL/Kerb docs to figure out how to turn that into appropriate Kerberos config etc.

Issue Links

• relates to: DISPATCH-213 Qpid dispatch management tools need explanation of hidden SASL conventions