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.
DescriptionJan Pazdziora (Red Hat)
2015-04-28 11:30:53 UTC
Description of problem:
Currently, the realm feature in Satellite 6 as documented at
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/User_Guide/Configuring_Identity_Management_in_Red_Hat_Satellite.html
only supports the setup when the Satellite (Capsule) machine is IPA-enrolled and provisioned machines will get identity in IdM.
It'd be good to relax the requirement of IPA-enrollment -- to run the host-add command, just the connection information and credentials to IdM server is needed, the Satellite OS (sssd, Kerberos, etc.) does not need to be configured towards the IdM server, or can use completely different IdM environment.
The requirements are:
- remove IPA-enrollment requirement for smart proxy (but use it for
the default case if IPA-enrolled);
- support multiple realms per smart proxy (this would immediately give
the "use different domain" feature);
- part of the realm configuration would be list of IPA servers to
connect to, or use of SRV records;
Version-Release number of selected component (if applicable):
Satellite 6.0 and 6.1.
How reproducible:
Deterministic.
Steps to Reproduce:
1. Attempt to set up the realm feature without having the Satellite (Capsule) machine IPA-enrolled, or set it up against different IdM server; or support multiple realms per smart proxy; fallback to SRV or OS-level IPA-enrollment if not specified otherwise.
Actual results:
The setup on non-IPA-enrolled machine is possible by hacking /etc/ipa/default.conf content to pretend the machine is IPA enrolled. Other parts of the requirements cannot be done with existing code base.
Expected results:
It is possible, easy, and supported to setup as outlined in requirements above.
Additional info:
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.