Bug 862561 - Support for ssl-require-client-authentication=yes
Support for ssl-require-client-authentication=yes
Status: CLOSED WONTFIX
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: cumin (Show other bugs)
2.2
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: grid-maint-list
MRG Quality Engineering
: FutureFeature
Depends On:
Blocks: 864997
  Show dependency treegraph
 
Reported: 2012-10-03 04:48 EDT by Stanislav Graf
Modified: 2016-05-26 16:23 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 864997 (view as bug list)
Environment:
Last Closed: 2016-05-26 16:23:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stanislav Graf 2012-10-03 04:48:17 EDT
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:
Comment 3 Anne-Louise Tangring 2016-05-26 16:23:26 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.