Description

As announced to the community in this blog post, we are no longer developing the Map Store, and it will be removed from Keycloak's codebase. This epic tracks the steps needed to completely remove it.

Discussion

See community blog post

Issues

• Map Store Removal: Create branch to hold map store bits #24088
• Map Store Removal: Remove Map Store tests from GHA #24089
• Map Store Removal: Deprecate and remove Getting Started guides in Github #24090
• Map Store Removal: Close issues on Github (cleanup) #24091
• Map Store Removal: Revisit documentation #24092
• Map Store Removal: Delete map profiles and scopes from model tests #24093
• Map Store Removal: Delete map profiles from testsuite #24094
• Map Store Removal: Delete retry blocks introduced for CockroachDB #24095
• Map Store Removal: Delete container providers that were added to the base testsuite #24097
• Map Store Removal: Delete map store related config options from quarkus #24098
• Map Store Removal: Rework build steps in KeycloakProcessor #24099
• Map Store Removal: Delete all code related to the store (modules map*) #24100
• Map Store Removal: Delete map dependencies from dependency management #24101
• Map Store Removal: Delete SearchableModelField #24722
• Remove Map storage from Keycloak Helm chart keycloak-benchmark#605
• Map Store Removal: Remove LockObjectsForModification #24793
• Map Store Removal: Revert changes related to map store in test classes in base testsuite #24567
• Map Store Removal: Delete Profile.Feature.MAP_STORAGE and all its usages #24102
• Map Store Removal: Delete GlobalLockProvider #24103
• Map Store Removal: Remove protostream dependency #25288
• Map Store Removal: Revert changes made to backchannelLogout #25308
• Map Store Removal: Remove ResponseSessionTask #25309
• Map Store Removal: Delete amphibian factory #24104
• Map Store Removal: Rename Legacy* classes #24105
• Map Store Removal: Revert deprecated modules in model/legacy and rename "legacy" to "storage" #24107
• Map Store Removal: Remove RealmModel from authorization services interfaces #26530
• Map Store Removal: Farewell virtual gathering #24110
• Map Store Removal: Revert changes related to export/import - LegacyExportImportManager #24108
• Map Store Removal: Discuss what to do with the new invalidations #24109
• Map Store Removal: Revisit changes in KeycloakSession #25896
• Map Store Removal: Remove unnecessary check in Jpa Connection Provider #26406

Motivation

Having both the current store and the Map Store in the codebase is greatly complicating maintenance, and other teams have a hard time working with the storage layer because any change has to be replicated in both stores. With the decision to no longer develop the Map Store, we should aim to remove it from the codebase to simplify both maintenance and further developments in the current store.