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.

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3-beta/html/installation_guide/installing_capsule_server

Section Number and Name:
4.6.1. Configuring Capsule Server with a Default Server Certificate -> 4. Enable the certificate based on the needs of your environment. For more information, see satellite-installer --help. 

Describe the issue: 
The capsule install command refers to non-existing options like:
--capsule-parent-fqdn
--capsule-pulp-oauth-secret

Suggestions for improvement:
--capsule-parent-fqdn should be ---foreman-proxy-content-parent-fqdn
--capsule-pulp-oauth-secret should be --foreman-proxy-content-pulp-oauth-secret

Additional information:

Assigning to Melanie for review.

These changes are now live on the 6.3-Beta Customer Portal. 

Thanks,

Melanie