Hide Forgot
Document URL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-file_and_print_servers#setting_up_samba_as_a_domain_member Section Number and Name: "16.1.5. Setting up Samba as a Domain Member" Describe the issue: With Samba 4.8+, we cannot use SSSD at all for joining a Samba server to an Active Directory environment. This documentation affirms "use Winbind to join", but it does not make any mention of SSSD, which is a much more popular option for our customers. Suggestions for improvement: Since Red Hat has been recommending using SSSD over Winbind for integrating to Active Directory, we would suggest adding an Alert box explaining that using Winbind is mandatory, and must be used in place of SSSD (the much more common, and otherwise recommended option). We're suggesting this because we're having to convince customers to switch from their current configuration using SSSD over to a Winbind configuration. Additional information: The following bug discusses the necessity for Winbind running with Samba 4.8+: "Bug 1624661 - Samba with security is set to ads fails to start after upgrade from 4.7.1-6 to 4.7.1-9." https://bugzilla.redhat.com/show_bug.cgi?id=1624661
We already have an <important> admonition about this: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-file_and_print_servers#the_samba_services (under "Winbindd"). > Red Hat only supports running Samba as a server with the winbindd service to > provide domain users and groups to the local system. Due to certain limitations, > such as missing Windows access control list (ACL) support and NT LAN Manager (NTLM) > fallback, the System Security Services Daemon (SSSD) is not supported. Is this sufficient?
Yes, thank you. We were thinking about a message possibly saying "SSSD is no longer supported" to address the cases where we're having to suggest changing a previously-working configuration, but we suppose that's not necessary.