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

Bug 1241525

Summary:	Document ACL user connection limit
Product:	Red Hat Enterprise MRG	Reporter:	Barbora Vassova <bvassova>
Component:	Messaging_Installation_and_Configuration_Guide	Assignee:	Scott Mumford <smumford>
Status:	CLOSED ERRATA	QA Contact:	Michal Toth <mtoth>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1	CC:	mtoth, pmoravec
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	MICG: Add the new section specified in #Description into the guide. It is a relatively small section to incorporate.
Last Closed:	2015-10-08 13:10:47 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:

Description Barbora Vassova 2015-07-09 12:15:38 UTC

Description of problem:
The guide is missing an information about the RFE https://bugzilla.redhat.com/show_bug.cgi?id=1049833, specifically the option of adding a limitation of the IP addresses from which can the user connect ("create connection"), as described in upstream documentation http://qpid.apache.org/releases/qpid-0.30/cpp-broker/book/chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Authorization-Specifying_ACL_Connection_Host_Limits



Version-Release number of selected component (if applicable):
MRG 3.1

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Scott Mumford 2015-09-03 00:46:11 UTC

Taking ownership of MRG-M bugs

Comment 5 Michal Toth 2015-09-14 06:45:41 UTC

Verified against built MICG:
http://docbuilder.usersys.redhat.com/18173/#Connection_Limits_by_Hostname
Looks good to me.

Comment 7 errata-xmlrpc 2015-10-08 13:10:47 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-1879.html