Actions
Bug #38465
open
Permissions are not unique
Status:
New
Priority:
Normal
Assignee:
-
Category:
Users, Roles and Permissions
Target version:
-
Description
This all came up because of https://github.com/theforeman/foreman-documentation/pull/3271. Copying https://github.com/theforeman/foreman-documentation/pull/3271#issuecomment-2931361478.
- In Foreman 1.13 via #13529 duplicate permissions were forbidden via a unique index (954abbaf59154c90717f6b56d54fae9d8168d010)
- In Foreman 1.20 via #24256 this was (unintentionally) reverted (672149bad448513e455e90450241d01df2beb088)
- This was reported in #30527 when users upgraded to Foreman 1.22. There a foreman-maintain procedure was introduced instead of properly addressing the regression.
Updated by Ewoud Kohl van Wijngaarden about 1 year ago
- Related to Bug #13529: Duplicate permissions are allowed and not recognized added
Updated by Ewoud Kohl van Wijngaarden about 1 year ago
- Related to Refactor #24256: Get rid of useless db indices and imrpove index ordering added
Updated by Ewoud Kohl van Wijngaarden about 1 year ago
- Related to Bug #30527: Red Hat Satellite upgrade to 6.6 fails if duplicate permissions are present in foreman database added
Updated by Eric Helms 7 days ago
See also https://github.com/theforeman/foremanctl/pull/521#discussion_r3327895668 where a check exists in our installer tooling because of this issue. Ideally we could solve this regression and design a test that helps prevent it from coming back.
Updated by Quinn James 7 days ago
+1 to Eric's comment. When completing this issue, please create a new issue in https://github.com/theforeman/foremanctl/issues requesting the removal of the `check_duplicate_permissions` role in the release following this Foreman version.
Actions