Description of problem:
SSSD with the AD provider sets 'ldap_schema' to 'ad', but it does not forbid or warn users from manually changing the schema to something different like 'rfc2307'. This may result in some unwanted effects where pure RfC2307 based objects stored in AD can not be resolved successfully.
The ask here is to give a warning in the log files when 'id_provider' is set to 'ad' but 'ldap_schema' is set to something different than 'ad'. An additional note in sssd-ad man page would also help to avoid such problems.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Configure sssd.conf as below:
domains = juno.test
config_file_version = 2
services = nss, pam
ad_domain = juno.test
krb5_realm = JUNO.TEST
realmd_tags = manages-system joined-with-samba
cache_credentials = True
id_provider = ad
ldap_schema = rfc2307
krb5_store_password_if_offline = True
default_shell = /bin/bash
ldap_id_mapping = True
use_fully_qualified_names = True
fallback_homedir = /home/%u@%d
access_provider = ad
debug_level = 9
2. Restart sssd
3. Following log message is shown in log_<ad-domain>.log
(Sun Jul 15 02:14:17 2018) [sssd[be[juno.test]]] [ad_set_sdap_options] (0x0040): The AD provider only supports the AD LDAP schema. SSSD will ignore the ldap_schema option value and proceed with ldap_schema=ad
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.