Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-4593

Support having large number of realms

    XMLWordPrintable

Details

    • Documentation (Ref Guide, User Guide, etc.)
    • NEW
    • NEW

    Description

      At the moment there are issues with having larger (100+) amount of realms on a single server. We need to investigate and improve this. Known issues are:

      • Queries not optimized for many realms
      • Caches could have issues
      • Master admin "tokens" to big
      • Version upgrade migration takes too long as realms increase

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. KEYCLOAK-12450 Realm cache disabling blocks authentication to admin console

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KEYCLOAK-9354 New storage layer prototype

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. KEYCLOAK-1268 Token for admin becomes to large with many realms

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement or refactoring of existing functionality KEYCLOAK-4858 Slow query performance for client with large data volume

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement or refactoring of existing functionality KEYCLOAK-13818 Reduce number of calls to get client scopes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. KEYCLOAK-4872 MSSQL realm creation/deletion deadlocks

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: KEYCLOAK

              People

                Unassigned Unassigned
                sthorger@redhat.com Stian Thorgersen
                Votes:
                50 Vote for this issue
                Watchers:
                68 Start watching this issue

                Dates

                  Created:
                  Updated: