Skip to content

fix(user_ldap): do not cache missing mappings in getDNByName - #66098

Open
lazerg wants to merge 1 commit into
nextcloud:masterfrom
lazerg:fix/issue-66003-ldap-mapping-cache-miss
Open

lazerg wants to merge 1 commit into
nextcloud:masterfrom
lazerg:fix/issue-66003-ldap-mapping-cache-miss

Conversation

@lazerg

@lazerg lazerg commented Oct 31, 2026 •

Copy link
Copy Markdown

Summary

getDNByName() cached a miss (false) in the local mapping cache for 30 days, and the CLI never refreshes that cache, so a user mapped later by occ ldap:search or the sync job stayed unknown to web requests. Now only found DNs are cached.

AI (if applicable)

  • The content of this PR was partly or fully generated using AI

Written with Claude (claude-opus-5-5). I have not run the test suite locally.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: lazerg <lazerg2@gmail.com>
@lazerg
lazerg requested a review from a team as a code owner October 31, 2026 08:04
@lazerg
lazerg requested review from CarlSchwan, artonge and cristianscheid and removed request for a team October 31, 2026 08:04

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

user_ldap: a lookup before mapping is cached for 30 days, so the user stays unknown in web requests after the sync or occ ldap:search maps them

1 participant