Bug 988081 - Check certs into SVN
Check certs into SVN
Status: CLOSED EOL
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Backend (Show other bugs)
AMS Backlog
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Richard Bernleithner
Narayanan Raghavan
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-24 13:07 EDT by Brooks
Modified: 2017-07-05 11:12 EDT (History)
3 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-07-24 13:07:27 EDT
Description of Enhancement:

 

The self-service Satellite Certificate Portal tool should check all generated certificates into the existing Satellite Certificate repository just like all certificates generated via internal GSS Sat Cert tool and manual cert creations.

 

What is the subversion server name?

- See https://satcert.gsslab.rdu2.redhat.com/viewvc/svnrepos/trunk/pm/satellite-certs/

- directories are based on Satelltie version, so Satellite 5.5 Certificates would go under "satellite-5.5", for example

 

User name / Password for server ?

Shea will get a User Name / Password before this is placed into sprint


Maybe new users needed?

- yes let's use a new one for the Portal tool

- who owns the svn server? probably Nilesh Patil

 

File naming convention?

- so far looks like it's named based on the Organization name, possibly with some other information

 

Actual Results:

Currently certificates generated via Portal tool are stored into production db as CLOB only.

 

Expected results:

Instead, every certificate generated should be checked into the existing Satellite Certificate svn repo under the correct subdirectory corresponding to the Satellite version (see the subdirectories under https://satcert.gsslab.rdu2.redhat.com/viewvc/svnrepos/trunk/pm/satellite-certs/ e.g., satellite-5.6).

 

 

Additional info:

Future effort/todo: the existing certs in the db needs to be exported and checked into the repo.

This bug was created from the contents in https://docspace.corp.redhat.com/docs/DOC-151458 which was collaboratively created by members of the IT-Eng team and AMS as well as others.
Comment 1 Brooks 2013-07-24 13:08:45 EDT
US36637 added to AMS Backlog. Ready for Prioritization.
Comment 7 Thomas "Shea" DeAntonio 2017-07-05 11:11:03 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 8 Thomas "Shea" DeAntonio 2017-07-05 11:12:19 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.