Project

General

Custom queries

Profile

Actions
Copy link

Bug #10492

closed

validate permission name should be unique and not scoped by resource_type

Added by Joseph Magen almost 10 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Joseph Magen
Category:
Users, Roles and Permissions
Target version:
1.9.0
Difficulty:
Triaged:
Bugzilla link:
1221343
Pull request:
https://github.com/theforeman/foreman/pull/2377
Fixed in Releases:
Found in Releases:
Red Hat JIRA:
Actions
Copy link
 #1

Updated by Joseph Magen almost 10 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
Actions
Copy link
 #2

Updated by The Foreman Bot almost 10 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2377 added
  • Pull request deleted ()
Actions
Copy link
 #3

Updated by Joseph Magen almost 10 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
Actions
Copy link
 #4

Updated by Bryan Kearney almost 10 years ago

  • Bugzilla link set to 1221343
Actions
Copy link
 #5

Updated by Dominic Cleal almost 10 years ago

  • Translation missing: en.field_release set to 35
Actions
Copy link
 #6

Updated by Joseph Magen almost 10 years ago

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

Also available in: Atom PDF