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.
DescriptionRam Nainsingh Tiruwa
2019-12-30 06:16:20 UTC
cross-forest realm auth doesn't fetch user info from Active Directory automatically in the satellite.
Satellite 6.5
Integrated cross-forest realm to point Satellite server to IDM and IDM to one way trusted to AD
when AD-User tries to login first-time satellite does not fetch First Name, Last Name, and Email Address from AD.
whenever AD-User is logged satellite should fetch the user info (First Name, Last Name, and Email Address) from AD.
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Closing this bug out since we do not believe it will be fixed in the next multiple releases due to our current available capacity and the amount of external dependencies looking into this would require. If this is a large impact on you, please feel free to re-open it and provide additional information to help us better prioritize it.