The recommended way to configure a System Security Services Daemon (SSSD) client to an Active Directory (AD) domain is using the realmd suite. If you do not want to use realmd, this procedure describes how to configure the system manually.
The recommended way to configure a System Security Services Daemon (SSSD) client to an Active Directory (AD) domain is using the realmd suite. See the Windows Integration Guide.
If you do not want to use realmd, this procedure describes how to configure the system manually.
Set up the Linux system as an AD client and enroll it within the AD domain. This is done by configuring the Kerberos and Samba services on the Linux system.
Install the following packages:
# yum install krb5-workstation samba-common-tools sssd-ad
Set up Kerberos to use the AD Kerberos realm.
Open the Kerberos client configuration file.
# vim /etc/krb5.conf
[libdefaults]sections so that they connect to the AD realm.
[logging] default = FILE:/var/log/krb5libs.log [libdefaults] default_realm = EXAMPLE.COM dns_lookup_realm = true dns_lookup_kdc = true ticket_lifetime = 24h renew_lifetime = 7d rdns = false forwardable = yes
If auto-discovery is not used with SSSD, then also configure the
[domain_realm]sections to explicitly define the AD server.
Configure the Samba server to connect to the AD server.
Open the Samba configuration file.
# vim /etc/samba/smb.conf
Set the AD domain information in the
[global] workgroup = EXAMPLE client signing = yes client use spnego = yes kerberos method = secrets and keytab log file = /var/log/samba/%m.log password server = AD.EXAMPLE.COM realm = EXAMPLE.COM security = ads
Add the Linux machine to the AD domain.
Obtain Kerberos credentials for a Windows administrative user.
# kinit Administrator
Add the machine to the domain using the
# net ads join -k Joined 'server' to dns domain 'example.com'
This creates a new keytab file,
List the keys for the system and check that the host principal is there.
# klist -k
If necessary, install the
oddjob-mkhomedirpackage to allow SSSD to create home directories for AD users.
# yum install oddjob-mkhomedir
authconfigto enable SSSD for system authentication. Use the
--enablemkhomedirto enable SSSD to create home directories.
# authconfig --update --enablesssd --enablesssdauth --enablemkhomedir
Open the SSSD configuration file.
# vim /etc/sssd/sssd.conf
Configure the AD domain.
[sssd]section, add the AD domain to the list of active domains. This is the name of the domain entry that is set in [domain/NAME] in the SSSD configuration file.
pacto the list of services; this enables SSSD to set and use MS-PAC information on tickets used to communicate with the AD
[sssd] config_file_version = 2 domains = ad.example.com services = nss, pam, pac
Create a new domain section at the bottom of the file for the AD domain. This section has the format domain/NAME, such as
domain/EXAMPLE. For each provider, set the value to
ad, and give the connection information for the specific AD instance to connect to.
[domain/AD.EXAMPLE] id_provider = ad auth_provider = ad chpass_provider = ad access_provider = ad
Enable credentials caching; this allows users to log into the local system using cached information, even if the AD domain is unavailable.
cache_credentials = true