Bug #10492
validate permission name should be unique and not scoped by resource_type
Status:
Closed
Priority:
Normal
Assignee:
Category:
Users, Roles and Permissions
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Associated revisions
History
#1
Updated by Joseph Magen almost 8 years ago
Updated by - Subject changed from role.add_permission doesn't account for when multiple permission entries exist in the DB with the same permission name but different resource_type values to role.add_permissions doesn't account for when multiple permission entries exist in the DB with the same permission name but different resource_type values
#2
Updated by The Foreman Bot almost 8 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2377 added
- Pull request deleted (
)
#3
Updated by Joseph Magen almost 8 years ago
- Subject changed from role.add_permissions doesn't account for when multiple permission entries exist in the DB with the same permission name but different resource_type values to validate permission name should be unique and not scoped by resource_type
#4
Updated by Bryan Kearney almost 8 years ago
Updated by - Bugzilla link set to 1221343
#5
Updated by Dominic Cleal almost 8 years ago
Updated by - Legacy Backlogs Release (now unused) set to 35
#6
Updated by Joseph Magen almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 04ad52f78f83954bec062a48a0ee3cd7d35bb9dd.
fixes #10492 - permission name should be unique and not scoped by resource_type