Page MenuHomePhabricator

Bitu not importing key changes directly in LDAP
Closed, ResolvedPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

What happens?:
Newly added key is missing.

What should have happened instead?:
Newly added key shows up.

Software version (skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):

Event Timeline

SLyngshede-WMF changed the task status from Open to In Progress.Mar 21 2024, 2:09 PM
SLyngshede-WMF claimed this task.
SLyngshede-WMF triaged this task as High priority.

Okay, I see the issue. In order to not hit LDAP to much, keys are cached, but that's honestly no good as that gives the users a false impression of what keys are active.

Change #1013442 had a related patch set uploaded (by Slyngshede; author: Slyngshede):

[operations/software/bitu@master] Let Bitu be a little more aggressive with loading SSH keys from LDAP.

https://gerrit.wikimedia.org/r/1013442

Change #1013442 merged by jenkins-bot:

[operations/software/bitu@master] Let Bitu be a little more aggressive with loading SSH keys from LDAP.

https://gerrit.wikimedia.org/r/1013442

That fixed the synchronization with other services, but makes it slightly trigger to actually delete keys.

There will be a followup patch.

Change #1013507 had a related patch set uploaded (by Slyngshede; author: Slyngshede):

[operations/software/bitu@master] Keymanagement: Bypass job queue for ssh key operations.

https://gerrit.wikimedia.org/r/1013507

Change #1013507 merged by jenkins-bot:

[operations/software/bitu@master] Keymanagement: Bypass job queue for ssh key operations.

https://gerrit.wikimedia.org/r/1013507

SLyngshede-WMF moved this task from Pending Release to Resolved on the Bitu board.