Project

General

Profile

Actions

Bug #32396

closed

Permissions for import/export

Added by Partha Aji about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Roles and Permissions
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

With auto create functionality importing things into a content view requires multiple high level permissions currently including product create/update, repo create/update, cv create/update along with import_content_views. Handling this wide array of permissions adds complexity to the code

Proposal:
Change permissions needed to export and import content
  • To import you need organization 'import_content'
  • To export you need organization 'export_content'

Both are at org level so its amply clear to the user that its going to be creating stuff in the library that they have no control over.

Steps to address this proposal:

  • Scour through content_exports_controllers and content_import_controllers for permissions that need to be tweaked.
  • Add a 'Content Importer' role that only include organization 'import_content' permission
  • Add a 'Content Exporter' role that only include organization 'export_content' permission
Actions #1

Updated by James Jeffers almost 3 years ago

  • Triaged changed from No to Yes
Actions #2

Updated by The Foreman Bot almost 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/9354 added
Actions #3

Updated by Jeremy Lenz almost 3 years ago

  • Triaged changed from Yes to No
Actions #4

Updated by Samir Jha almost 3 years ago

  • Triaged changed from No to Yes
Actions #5

Updated by The Foreman Bot almost 3 years ago

  • Fixed in Releases Katello 4.2.0 added
Actions #6

Updated by Lucy Fu almost 3 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF