Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 88997 - [RFE] Option to prevent users from manually viewing/downloading/installing errata and packages
Summary: [RFE] Option to prevent users from manually viewing/downloading/installing er...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Nightly
Hardware: All
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: Todd Warner
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 248475
Blocks: sat-nextgen
TreeView+ depends on / blocked
 
Reported: 2003-04-16 08:42 UTC by Albert Castillo
Modified: 2021-08-04 15:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-16 17:54:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-4494 0 None None None 2021-08-01 22:13:57 UTC

Description Albert Castillo 2003-04-16 08:42:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; Q312461)

Description of problem:
1) I would like some additional user options so that I (as an Enterprise 
administrator) can:
    a) Prevent a user from viewing errata/packages that are
       available for his machine (in the system tray applet).
    b) Prevent a user from manually downloading/installing errata
       and packages (by launching "up2date")

This would allow me to prevent a user from viewing and/or attempting to install 
errata and packages. In my case, I want to fully control what is installed on 
the user's system and do not want to allow him to initiate (or even see) any 
errata/packages that are available.

2) I would also like an additional option that would allow me (as an 
administrator) to specify the following for a user:
   a) Only allow a user to view/download/install the errata and
      packages that I specify for him.
 or
   b) Allow a user to view/download/install everything. This is how
      RHN Enterprise currently works.

Version-Release number of selected component (if applicable):
Enterprise

How reproducible:
Always

Steps to Reproduce:
1. NA
2.
3.
    

Additional info:

Comment 1 Fanny Augustin 2006-11-14 20:37:26 UTC
Reassigning  bugs from gdk (old RHN engineering Manager) to tsanders (current
RHN engineering manager)

Comment 4 Clifford Perry 2010-10-13 18:16:19 UTC
This has overlap with bug 248475. The other bug though only talks about preventing client side, up2date/yum from pulling down content if system is 'locked'. This bug goes further in asking for UI lock down also. 

Cliff

Comment 7 Mike McCune 2013-08-16 17:54:43 UTC
NACKing this.  We aren't going to be implementing this directly. 

Maintenence windows may help and if a customer feels strongly about this specific use case above we can re-open.


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