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

Bug 654422

Summary:	mrg-el4 - Need mechanism to limit access to QMF Agent methods
Product:	Red Hat Enterprise MRG	Reporter:	Ted Ross <tross>
Component:	qpid-qmf	Assignee:	messaging-bugs <messaging-bugs>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Reznicek <freznice>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.3	CC:	esammons, freznice, gsim, iboverma, jneedle, jsarenik, matt
Target Milestone:	1.3.0.1	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Prior to this update, no mechanism to limit access to QMFv2 Agent methods was available. With this update, an API hook was provided so that agent applications can perform their own access control based on an authentic identity.	Story Points:	---
Clone Of:	649822	Environment:
Last Closed:	2010-11-30 18:01:44 UTC	Type:	---
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:	649822
Bug Blocks:	644041, 649919

Comment 1 Frantisek Reznicek 2010-11-18 14:59:13 UTC

The feature has been implemented, see details here:
https://bugzilla.redhat.com/show_bug.cgi?id=649822#c10


-> VERIFIED

Comment 3 errata-xmlrpc 2010-11-30 18:01:44 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0922.html

Comment 4 Martin Prpič 2010-12-01 14:35:15 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Prior to this update, no mechanism to limit access to QMFv2 Agent methods was available. With this update, an API hook was provided so that agent applications can perform their own access control based on an authentic identity.