#50790 Add notification that filter was process differently based on invalid attr
Closed: wontfix 4 years ago by firstyear. Opened 4 years ago by firstyear.

Issue Description

Given an invalid attr we should return an err message in the ldap result to notify that the results may be truncated due to an invalid filter component.

Package Version and Platform

1.4.2 onward

Steps to reproduce

1.
2.
3.

Actual results

Expected results


Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

4 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.2

4 years ago
To ssh://pagure.io/389-ds-base.git
   c5541085e..b8f99b73b  389-ds-base-1.4.2 -> 389-ds-base-1.4.2
To ssh://pagure.io/389-ds-base.git
   de5e4acff..46daeac58  389-ds-base-1.4.1 -> 389-ds-base-1.4.1

PR merged also to 1.4.3. Thanks everyone :)

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3845

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata