Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 862561

Summary:	Support for ssl-require-client-authentication=yes
Product:	Red Hat Enterprise MRG	Reporter:	Stanislav Graf <sgraf>
Component:	cumin	Assignee:	grid-maint-list <grid-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.2	CC:	iboverma, matt, tmckay
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	864997 (view as bug list)		Environment:
Last Closed:	2016-05-26 20:23:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	864997

Description Stanislav Graf 2012-10-03 08:48:17 UTC

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 20:23:26 UTC

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.