Repository navigation
[#1296] Document LDIF backend configuration and proxy suffix limitations - #1298
Merged
vharseko merged 2 commits intoNov 16, 2026
Merged
Conversation
…roxy suffix limitations
maximthomas
approved these changes
Nov 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add the missing administration-guide procedure for configuring and operating the built-in LDIF backend. The chapter covers its in-memory reads and file rewrites, single base DN, backing-file path, enablement, write policy, and limited custom-control support. It includes a minimal LDIF file,
dsconfig create-backend --type ldif, verification steps, and a safe procedure for editing and reloading static data.Explain how a local LDIF parent suffix coexists with subordinate proxy backends. A subtree search that reaches an unavailable child route still returns
UNAVAILABLE (52), even when some entries have already been returned or the LDIF file contains copies of child base entries. The chapter makes the boundaries of runtime fallback, result reconciliation, and federation explicit.Validation
git diff --checkpassed.Fixes #1296
Related to #1292 and discussion #554.