Project

General

Profile

Actions

Bug #12118

closed

AssociationAuthorizer should ask model for alternative permission names

Added by Stephen Benjamin over 8 years ago. Updated over 5 years ago.

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

Description

Current assumes some magic: a House model would always be "view_houses", but maybe you want a different permission name. Especially for plugins the code generates stuff like "view_foreman_salt/houses"


Related issues 1 (0 open1 closed)

Has duplicate Foreman - Bug #11408: Plugin permissions are broken when using multiple selectsDuplicate08/18/2015Actions
Actions #1

Updated by The Foreman Bot over 8 years ago

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

Updated by Dominic Cleal over 8 years ago

  • translation missing: en.field_release set to 63
Actions #3

Updated by Anonymous over 8 years ago

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

Updated by Stephen Benjamin over 8 years ago

  • Has duplicate Bug #11408: Plugin permissions are broken when using multiple selects added
Actions

Also available in: Atom PDF