Skip to content

chart/4.23.14

  • chart/4.23.14
  • 7a5e718

  • Partially verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
  • Compare
    Choose a tag to compare
chart/4.23.14: Make deletions via SCIM more stable (#2637)
  • chart/4.23.14
  • 7a5e718
  • Compare
    Choose a tag to compare

  • Partially verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
@supersven supersven tagged this 08 Sep 06:03 
Cassandra doesn't support transactions. Thus, in rare circumstances, a user
could be only partially deleted in brig (e.g. due to the pod shutting down). To
be able to clean up a partially deleted user/account, the SCIM user deletion
handler now executes the internal deletion function in brig again even if the
user is not found in brig as it's only a "tombstone". This internal deletion
function then figures out if the user ever existed and if there are any left
overs. In case, deletion is executed for the user/account again.

To gather the result of a user deletion, the brig endpoint is now synchronous
(was asynchronous before).

Co-authored-by: Matthias Fischmann <[email protected]>
Assets 2
Loading