Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-13933 Client Policies
  3. KEYCLOAK-17932

Use KeycloakSession.getComponentProvider for executors and conditions to achieve good performance

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 14.0.0
    • Component/s: None
    • Labels:
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      I think that performance of Client policies is probably not so great right now, as every request to "DefaultClientPolicyManager.triggerOnEvent" needs to create all condition provider instances and similarly request to "DefaultClientPolicyManager.doPolicyOperation" needs to create all executor provider instances.

      It will be probably good to re-use AmphibianProviderFactory to avoid creation of providers all over again and achieve good performance.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mposolda@redhat.com Marek Posolda
              Reporter:
              mposolda@redhat.com Marek Posolda
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: