Bug 1289676 - Scheduled reports generate for last group selected by user when user is a member of multiple groups
Summary: Scheduled reports generate for last group selected by user when user is a mem...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: 5.6.0
Assignee: Libor Pichler
QA Contact: Jiri Stefanisin
URL:
Whiteboard:
Depends On:
Blocks: 1289687 1289688
TreeView+ depends on / blocked
 
Reported: 2015-12-08 17:29 UTC by Gregg Tanzillo
Modified: 2016-06-29 15:18 UTC (History)
4 users (show)

Fixed In Version: 5.6.0.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1289687 1289688 (view as bug list)
Environment:
Last Closed: 2016-06-29 15:18:26 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Gregg Tanzillo 2015-12-08 17:29:32 UTC
When a user schedules a report to run, the schedule record contains the user's ID, but not the group's ID.  When the report actually runs, the group that is used to run the report is based on the last group the user logged in as (as noted above).  Not only does this label that saved report with a potentially different group each time, but the saved report's content is based on the group's RBAC filters, so that means each report might have different content.

Comment 5 errata-xmlrpc 2016-06-29 15:18:26 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://access.redhat.com/errata/RHBA-2016:1348


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