-
Story
-
Resolution: Done
-
Major
-
RH362 - RHEL 9.1 0, RH362 - RHEL 7.4 1 20180531
-
en-US (English)
URL:
Reporter RHNID:
Section: -
Language: en-US (English)
Workaround:
Description: Guided Exercise: Accessing Active Directory Using Direct Integration
Remove the whole winbind portions from the GE.
Focus on the most common use case of direct connect instead of IdM trust which is the samba server that is used by windows clients. We have a new enough version of RHEL to use sssd as recommended and no need for winbind.
Per the narration, we do not have any need
"Prior to Red Hat Enterprise Linux 7.1, Winbind was the service that was accessing Samba shares. In Red Hat Enterprise Linux 7.1 and later, you no longer need to run Winbind and SSSD in parallel to access Samba shares."
and
"For most SSSD clients, Red Hat recommends using SSSD, as IdM uses SSSD by default to map Active Directory users to UNIX users. Using Winbind for mapping Samba users to Linux users, instead of using SSSD can result in inconsistent mapping."
This will require modifications to step 2 (much of step 2 is still required for SSSD implantation), setting up direct connect with sssd before working with samba, removing the remove step (step 5)
- relates to
-
PTL-7314 RH362-66: Ch 5 AD direct connection needs to be split or trimmed. Too long!
- Closed