This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2264601 - IDM + AD + Cross Forest configuration
Summary: IDM + AD + Cross Forest configuration
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Authentication
Version: 6.14.1
Hardware: All
OS: All
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-16 20:11 UTC by Waldirio M Pinheiro
Modified: 2024-08-19 07:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:03:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-23355 0 None Migrated None 2024-08-19 07:37:02 UTC

Description Waldirio M Pinheiro 2024-02-16 20:11:57 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/installing_satellite_server_in_a_connected_network_environment/index#Configuring_the_FreeIPA_Server_to_use_Cross_Forest_Trust_satellite

Section Number and Name: 
5.3.6. Configuring the Red Hat Identity Management Server to Use Cross-Forest Trust

Describe the issue: 
The customer can proceed with the steps mentioned. However, the login on Satellite will not work properly when trying to authenticate using one AD account. It will only work for IDM users.

Suggestions for improvement: 

From (current conf)
---
[nss]
user_attributes=+mail, +sn, +givenname
[domain/EXAMPLE.com]
...
krb5_store_password_if_offline = True
ldap_user_extra_attrs=email:mail, lastname:sn, firstname:givenname

[ifp]
allowed_uids = ipaapi, root
user_attributes=+email, +firstname, +lastname
---

To
---
[domain/EXAMPLE.com]
...
krb5_store_password_if_offline = True
ldap_user_extra_attrs=email:mail, lastname:sn, firstname:givenname

[nss]
user_attributes=+email, +firstname, +lastname

[ifp]
allowed_uids = ipaapi, root
user_attributes=+email, +firstname, +lastname
---

Note. Above, only the NSS section was updated. 

Also, reinforce that this configuration should be applied only on the IDM server(s), this will not be necessary on Satellite server itself.


One additional enhancement in the same section is, that there is one example of how to verify, using the DBUS command. It's valid to add another note mentioning that this command should be executed on IDM and Satellite Server, and the output should be the same on both, below you can see an example:
---
# dbus-send --print-reply --system --dest=org.freedesktop.sssd.infopipe /org/freedesktop/sssd/infopipe org.freedesktop.sssd.infopipe.GetUserAttr string:user1 array:string:email,firstname,lastname
method return time=1708114064.187163 sender=:1.330 -> destination=:1.334 serial=8 reply_serial=2
   array [
      dict entry(
         string "email"
         variant             array [
               string "user1"
            ]
      )
      dict entry(
         string "firstname"
         variant             array [
               string "First Name User1"
            ]
      )
      dict entry(
         string "lastname"
         variant             array [
               string "Last Name User1"
            ]
      )
   ]
---


Additional information: 

I'm not sure if you believe it to be valid, but, assuming the customer apply the change above, eventually, this will not be replicated in that moment, causing some sort of confusion, in order to guarantee this change is in effect, we can provide the step below
---
systemctl stop sssd ; rm -rf /var/lib/sss/{db,mc}/* ; systemctl start sssd
---

This will guarantee that there is no cache, and that the latest information will be available on idm and client (on this case, satellite server)

Comment 2 Eric Helms 2024-06-06 17:03:19 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


Note You need to log in before you can comment on or make changes to this bug.