New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to reject internal unindexed searches #4245
Comments
Comment from mreynolds (@mreynolds389) at 2020-06-29 16:32:24 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2020-06-29 16:32:25 Issue linked to Bugzilla: Bug 1851975 |
Comment from mreynolds (@mreynolds389) at 2020-06-29 20:53:10 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2020-06-29 23:52:36 |
Comment from mreynolds (@mreynolds389) at 2020-06-29 23:52:37 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2020-07-01 15:08:33 Commit 53f92181 relates to this ticket |
Comment from mreynolds (@mreynolds389) at 2020-07-01 15:09:45
|
Comment from mreynolds (@mreynolds389) at 2020-07-01 15:09:46 Metadata Update from @mreynolds389:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/51192
Issue Description
The current implementation of nsslapd-require-index for backends does not apply to internal operations. There are cases where we would want to block internal unindexed searches, so we should add a new option.
We should also log the filter and scope that is causing the search to be unindexed. This should be done for nsslapd-require-index and for the new setting
The text was updated successfully, but these errors were encountered: