Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
When a user installs the ca-cert file from /pub on a satellite, part of what it does is go ahead and update rhsm.conf with the appropriate settings for eventual registration of client to satellite. This is very convenient.
We should have a similar analogue when creating/using the certs tar.
Pressently, after running `capsule-certs-generate` on Satellite, user is given a very long (and not easily pasteable) `capsule-installer` and associated string of flags, which includes various oauth keys/secrets parsed from locations across a sat6 install.
The RFE here is to package the oauth credentials into the certs.tar and store it somewhere that can be retrieved during install. Just as we prepopulate rhsm.conf when doing katello ca cert, it seems it would be similarly useful to prepopulate this oauth stuff somewhere else, so user doesn't have to manually input on an install attempt.
Less stuff entered at install time = less room for error.