Uploaded image for project: 'Red Hat build of Keycloak'
  1. Red Hat build of Keycloak
  2. RHBK-4012

When syncing roles, the database layer can see deadlocks [GHI#43682]

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description

      When user data is synchronized for example with mappers on SAML login, roles are removed when they don't exist. As the DB code is using excessive locking, this is both slow and leads to deadlocks on concurrent logins.

      Value Proposition

      Better performance, and no deadlocks that slow down Keycloak and annoy users.

      Goals

      All user methods that update the user should in the caching layer first check if there is actually a change. Most of the time there is no change when synchronizing users.

      Non-Goals

      Other entities

      Discussion

      No response

      Notes

      I'll create a PR

              Unassigned Unassigned
              pvlha Pavel Vlha
              Keycloak SRE
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: