Project

General

Profile

Bug #10492

validate permission name should be unique and not scoped by resource_type

Added by Joseph Magen over 5 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Users, Roles and Permissions
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Associated revisions

Revision 04ad52f7 (diff)
Added by Joseph Magen over 5 years ago

fixes #10492 - permission name should be unique and not scoped by resource_type

History

#1 Updated by Joseph Magen over 5 years ago

  • 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 over 5 years ago

  • 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 over 5 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 over 5 years ago

  • Bugzilla link set to 1221343

#5 Updated by Dominic Cleal over 5 years ago

  • Legacy Backlogs Release (now unused) set to 35

#6 Updated by Joseph Magen over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF