Description of problem: Recently python clients (qpid-stat, qpid-config, qpid-tool) from Messaging started to support option 'ssl-require-client-authentication=yes'. What does this option do? Forces clients to authenticate in order to establish an SSL connection. Who can be affected? When users start using this option cumin stops working over ssl, but diagnostic python tools will still work. See linked BZs for more information. Version-Release number of selected component (if applicable): cumin-0.1.5444-3 How reproducible: 100% Steps to Reproduce: 1. Setup broker with 'ssl-require-client-authentication=yes' 2. Try to use cumin-broker configuration with SSL according to MCIG Actual results: cumin doesn't connect to broker Expected results: cumin set according to documentation works over ssl I propose: a) mention unsupported 'ssl-require-client-authentication=yes' in MCIG b) fix cumin to work with both (yes/no) authentication options Additional info:
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.