Bug 1571526 - SSSD with ID provider 'ad' should give a warning in case the ldap schema is manually changed to something different than 'ad'.
Summary: SSSD with ID provider 'ad' should give a warning in case the ldap schema is m...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: sssd-qe
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-25 05:08 UTC by Thorsten Scherf
Modified: 2020-05-02 18:57 UTC (History)
11 users (show)

Fixed In Version: sssd-1.16.2-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-10-30 10:42:26 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4735 0 None closed SSSD with ID provider 'ad' should give a warning in case the ldap schema is manually changed to something different than... 2020-10-21 01:49:08 UTC
Red Hat Product Errata RHSA-2018:3158 0 None None None 2018-10-30 10:43:46 UTC

Description Thorsten Scherf 2018-04-25 05:08:52 UTC
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):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 3 Jakub Hrozek 2018-04-30 13:32:34 UTC
Upstream ticket:

Comment 4 Fabiano Fidêncio 2018-05-03 20:08:55 UTC

Comment 7 Niranjan Mallapadi Raghavender 2018-07-15 06:16:39 UTC
1. Versions:

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

Comment 9 errata-xmlrpc 2018-10-30 10:42:26 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.