Bug 501611 - [RFE] Marking channels as disabled, or unavailable
[RFE] Marking channels as disabled, or unavailable
Status: CLOSED WONTFIX
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management (Show other bugs)
6.0.4
All Linux
low Severity low (vote)
: Unspecified
: --
Assigned To: Jan Pazdziora
Katello QA List
: FutureFeature, Triaged
Depends On:
Blocks: 490912
  Show dependency treegraph
 
Reported: 2009-05-19 22:32 EDT by Issue Tracker
Modified: 2014-06-19 11:19 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-19 11:14:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Issue Tracker 2009-05-19 22:32:03 EDT
Escalated to Bugzilla from IssueTracker
Comment 1 Issue Tracker 2009-05-19 22:32:05 EDT
Customer want to disable the software channel on satellite server. Currently we have option in satellite called "Globally Subscribable:" on channel details page, if we disable the checkbox for specific channel then non channel admin users are not able to subscribe new systems to this channel. But if we use activation key created my channel administrator (who has access to this channel) to register the system then new systems get registered to channel. 

So customer want feature that if we disable any channel then channel content should be intact but new systems should not get registered to this channel by any way of registration and same channel should be unavailable for systems which are already registered to the channel.
This event sent from IssueTracker by jwest  [SEG - Feature Request]
 issue 294933
Comment 5 Mike McCune 2014-06-19 11:19:17 EDT
We are closing this as a WONTFIX but there are facilities built into Satellite 6 that support controlling access via our Roles Based Access Control mechanism such that you can indicate if a user should or should not have access to specific repositories managed on the Satellite.

You can subscribe systems to a Content View in Satellite 6 which is a 'view' into a series of repositories.  You can then add/remove specific repositories from this view which will grant and deny systems using the view access to that repository.

This requires no changes on the system side and can be used to virtually disable/enable repositories.

Note You need to log in before you can comment on or make changes to this bug.