Bug 410081 - [RFE] Addon features to RHN website
[RFE] Addon features to RHN website
Status: NEW
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
rhn500-satellite-beta
All Linux
low Severity low
: ---
: ---
Assigned To: rhn-dev-list
Red Hat Satellite QA List
:
Depends On:
Blocks: 414671
  Show dependency treegraph
 
Reported: 2007-12-04 05:57 EST by Jóhann B. Guðmundsson
Modified: 2010-10-06 10:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Jóhann B. Guðmundsson 2007-12-04 05:57:43 EST
Description of problem:

Not a bug an RFE

It would be good to know which license key is assign to which system 
System --> Overview --> System info --> License = "license Key" 

When receiving Red Hat end of subscription alert IS

"The following license is about to expire or the following license 
assigned to the following system is about to expire..."

This would help identify/keep track of which system/server is about to expire
and to be better to monitor which system/server has which license assign to them.

Another feature lacking is User history on the RHN website

As in the Organization Administrator should be able to see what which
users and when users logged and were from they logged ( IP )in and what they did
including his own history.

Even more advanced feature would be that the Organization Administrator
could restrict users to login from certain IP's or IP range. 
( stricter security )

To better keep track of users.

( Have had an incident regarding this where I needed a user history ) 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

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