You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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]>
SCIM user deletion suffered from a couple of race conditions. The user in now first deleted in spar, because this process depends on data from brig. Then, the user is deleted in brig. If any error occurs, the SCIM deletion request can be made again. This change depends on brig being completely deployed before using the SCIM deletion endpoint in brig. In the unlikely event of using SCIM deletion during the deployment, these requests can be retried (in case of error).
0 commit comments