-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
23.3 Backport of #55119 - Fix deadlock in LDAP assigned role update - take 2 #364
23.3 Backport of #55119 - Fix deadlock in LDAP assigned role update - take 2 #364
Conversation
This is an automated comment for commit f5000c1 with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page Successful checks
|
…ldap-role-update Fix deadlock in LDAP assigned role update
…gration-test Fix flaky LDAP integration tests
Fixed merge conflict from rebasing
2395e79
to
2195b38
Compare
…y::test_role_mapping
It looks like From my investigations, user's groups are updated properly inside |
Update of assigned roles (`GrantedRoles`) on `User` instance that occurs inside `LDAPAccessStorage` doesn't bubble up to `AccessStorate` and not broadcasted as an event to `AccessChangesNotifier` event handlers. Thus `AccessControl` that is held by `Context` never receives an event and is never updated, holding old instance of `User` with previous set of roles. `AccessControl` instances are cached for 600 seconds, so waiting for 600 + 10 seconds between sessions ensures that when user is logged in again, new `AccessControl` instance is created, and proper (updated `User`, with updated `GrantedRoles`) is created. This issue seems to be already fixed in upstream/master, but for now we are not going to backport it, just fix the test.
b3b191e
to
f5000c1
Compare
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix deadlock in LDAP assigned role update for non-existing ClickHouse roles (ClickHouse#55119 by @jmaicher, ClickHouse#56544 by @jmaicher)
re-doing incorrectly merged #353