From 5063d7f32370d33583d431a2ee063de2362bd933 Mon Sep 17 00:00:00 2001
From: Rich Megginson Contents
id="toc-ad_dyndns_server">ad_dyndns_server
ad_dyndns_server
for details. Example: ad_integration_join_parameters: "--user-principal
host/client007@EXAMPLE.COM"
A list of setting to be included into the [sssd]
section
+of the sssd.conf file. See sssd.conf man pages for details. Example:
ad_integration_sssd_settings:
+ - key: "configuration_name"
+ value: "configuration_value"
A list of custom setting to be included into the
[domain/$REALM]
section of the sssd.conf file. See
sssd.conf man pages for details. Example:
ad_integration_sssd_custom_settings:
- - key: "configuration_name"
- value: "configuration_value"
ad_integration_sssd_custom_settings:
+ - key: "configuration_name"
+ value: "configuration_value"
This is a boolean, default is false
. If
+true
, configure realmd.conf to remove the
+authselect
command from sssd-enable-logins
to
+avoid overwriting previous PAM/nsswitch changes, until RHEL-5101 is
+addressed.
The following is an example playbook to setup direct Active Directory
integration with AD domain domain.example.com
, the join
will be performed with user Administrator using the vault stored
password. Prior to the join, the crypto policy for AD SUPPORT with RC4
encryption allowed will be set.
- hosts: all
- vars:
- ad_integration_realm: "domain.example.com"
- ad_integration_password: !vault | …vault encrypted password…
- ad_integration_manage_crypto_policies: true
- ad_integration_allow_rc4_crypto: true
- roles:
- - linux-system-roles.ad_integration
- hosts: all
+ vars:
+ ad_integration_realm: "domain.example.com"
+ ad_integration_password: !vault | …vault encrypted password…
+ ad_integration_manage_crypto_policies: true
+ ad_integration_allow_rc4_crypto: true
+ roles:
+ - linux-system-roles.ad_integration
See README-ostree.md