#1404 AD provider should default to case-insensitive operation
Closed: Fixed None Opened 8 years ago by sgallagh.

Right now, the AD provider must have {{{case_sensitive = False}}} specified explicitly in the config file. This is because the behavior of this option affects not only the provider back-end, but also the responders. We need to add a special-case (or a new mechanism) for detecting the use of case-insensitive providers in the domain init functions so that the AD provider will always operate case-insensitively.


For AD provider we will always force case_sensitive = false regardless of the current setting in the sssd.conf. If someone set it to true manually there will be a warning in the debug log and the value will be ignored.

milestone: NEEDS_TRIAGE => SSSD 1.9.0 beta 5

Fields changed

type: task => defect

Fixed by:
- a6cbaf2
- 346f41f

milestone: SSSD 1.9.0 beta 5 => SSSD 1.9.0 beta 4
patch: 0 => 1
resolution: => fixed
status: new => closed

Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.9.0 beta 4

3 years ago

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/2446

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata