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.
Description of problem:
A DOMAIN user logging into Satellite doesn't have the Organization and Location displayed by default (only exists one of each). A local Linux user does see the default Org and Location.
Version-Release number of selected component (if applicable):
6.10
How reproducible:
See above
Steps to Reproduce:
1. See above
2.
3.
Actual results:
Expected results:
Additional info:
There is already a case open - Case #03154653
Hi,
* can you please share steps how to reproduce the issue
* by domain user you mean user authenticated by external source or is it Foreman account?
* that "local linux user" is authenticated in Satellite? Or is it using hammer?
I'll take the liberty to assume that this and BZ #2089828 are about the same thing and close this one as a duplicate. If you feel there's a difference between this one and BZ #2089828 that I missed, feel free to reopen.
*** This bug has been marked as a duplicate of bug 2089828 ***