Bug 993407 - Do not allow RHN API to populate 'Version' entries within RHSM SatCert creation tool IF user does not have access to create Cert with that specific version
Do not allow RHN API to populate 'Version' entries within RHSM SatCert creati...
Status: CLOSED EOL
Product: Red Hat Network
Classification: Red Hat
Component: RHN/API (Show other bugs)
AMS Backlog
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Richard Bernleithner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-05 16:52 EDT by Brooks
Modified: 2017-07-05 11:13 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
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 Brooks 2013-08-05 16:52:49 EDT
Description of problem:

The RHN API loads *some* SatCert versions into the 'Version' dropdown within the RHSM SatCert creation tool located here, https://access.redhat.com/management/distributor/distributors/create/satellite

After this bug is closed, the entries that are loaded into this dropdown should ONLY be ones that the customer has access too as per their active subscriptions. All other entries that the customer does not have access to should not be loaded into this dropdown.

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

How reproducible:
Every time

Steps to Reproduce:
1. Become user dean.tran@eb-services.com.au
2. Go to https://access.redhat.com/management/distributor/distributors/create/satellite
3. Select 'Version:' dropdown

Actual results:
This user does not have access to create a SatCert with the version of 5.6B, however the 5.6B version appears in the dropdown

Expected results:
Only versions that the user has access to create SatCert's with should appear in the drop down.

Additional info:

This was requested within TASK0007568 by Shea DeAntonio
Comment 1 Brooks 2013-08-05 16:54:18 EDT
US37161 added to AMS Backlog
Comment 2 Thomas "Shea" DeAntonio 2017-07-05 11:13:13 EDT
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).
Comment 3 Thomas "Shea" DeAntonio 2017-07-05 11:13:50 EDT
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

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