Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1571526
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: 1. 2. 3. Actual results: Expected results: Additional info:
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1571526
https://github.com/SSSD/sssd/pull/562
Metadata Update from @jhrozek: - Issue tagged with: PR
master: 3cff2c5
Metadata Update from @fidencio: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.2
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4735
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.