Bug 1130726

Summary: [RFE][keystone]: Add CADF notifications for role assignments
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-keystoneAssignee: Nathan Kinder <nkinder>
Status: CLOSED ERRATA QA Contact: Mike Abrams <mabrams>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aberezin, ajeain, ayoung, markmc, trichard, yeylon
Target Milestone: z2Keywords: FutureFeature, TestOnly, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/keystone/+spec/role-assignment-notifications
Whiteboard: upstream_milestone_juno-3 upstream_definition_approved upstream_status_implemented
Fixed In Version: openstack-keystone-2014.2-1.el7ost Doc Type: Enhancement
Doc Text:
With this release, keystone now emits CADF notifications for role assignment events, providing a more complete audit trail. Role assignment operations affect a user's access to cloud resources; keeping an audit trail of these actions can be important to detect malicious actions.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 18:20:34 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:

Description RHOS Integration 2014-08-17 04:03:03 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/role-assignment-notifications.

Description:

Expand on the notifications that are emitted from Keystone by adding support for role assignments.

Specification URL (additional information):

http://specs.openstack.org/openstack/keystone-specs/specs/juno/role-assignment-notifications.html

Comment 4 Arthur Berezin 2015-02-17 09:30:46 UTC
Setting priority to medium, this RFE covers only role assignment notifications, the rest should be covered by BZ#1166483

Comment 7 errata-xmlrpc 2015-03-05 18:20:34 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/RHBA-2015-0639.html