Skip to content

[1.0.0] Server filter handling RFC conformance. - #265

Merged
ChadSikorra merged 9 commits into
FreeDSx:mainfrom
ChadSikorra:upgrade/rfc-fixes-part1
Aug 12, 2026
Merged

[1.0.0] Server filter handling RFC conformance.#265
ChadSikorra merged 9 commits into
FreeDSx:mainfrom
ChadSikorra:upgrade/rfc-fixes-part1

Conversation

@ChadSikorra

Copy link
Copy Markdown
Contributor

This reorganizes the integration tests and adds a ton for various behavior described in the RFCs. The integration tests run across all backend types, so it's pretty comprehensive and can catch a lot. This is all focused on conformance to the RFCs but focused only on server side filter handling right now. This also contains other refactoring, as things have shifted a lot as the backend has evolved. I'll have another follow up for filtering then move on to other areas.

  * Decode extensibleMatch from BER (this was missed in the original decoding).
  * Evaluate an unrecognized matching rule as Undefined (4.5.1.7).
  * Use the attribute type's EQUALITY rule when an extensibleMatch omits one.
  * Treat a defined attribute the entry lacks as false.
  * Cover tagged variants and SUP subtypes when asserting on an attribute type.
  * Add filter RFC cases to the storage integration tests that run on ever backend.
  * Compare integers as integers in the backend.
  * Match approximately using the type's EQUALITY rule.
  * Compare DN assertion values unescaped.
  * Treat attribute options as an unordered, case-insensitive set (RFC 4512 2.5).
  * Sort by the ordering rule the key asks for, else the one the attribute declares, else its syntax.
… to think through how to make these sorts of attributes filterable.
@ChadSikorra
ChadSikorra merged commit 59239c2 into FreeDSx:main Aug 12, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant