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
There has been added new searchable field COMPOSITE_ROLE within #11816
Composite roles should be probably extracted into separate table and index should be added to support the search.
We might want to consider the fact that composite roles number grows significantly with more realms and clients. There could also be transitive relations and parent has as effective roles all its composite roles and also composite roles of the 1st level composites etc.
As discussed in the storage team, the first step should be to extract this as a new table.
As there could be many composite roles within a role, this should avoid a one-to-many relation as such a relation would load all entries. Instead, a PR should try to model it only with many-to-one relations.
Activity
[-]A way how to store and query composite roles[/-][+]Way to store and query composite roles[/+]ahus1 commentedon Jun 28, 2022
As discussed in the storage team, the first step should be to extract this as a new table.
As there could be many composite roles within a role, this should avoid a one-to-many relation as such a relation would load all entries. Instead, a PR should try to model it only with many-to-one relations.
This is related to the efforts in #11799
Store composite roles within its own table for JPA Map storage.
ahus1 commentedon Jul 4, 2022
Follow-up issue with the remaining tasks: #12888
Fixing broken build after merging conflicting PRs.
Fixing broken build after merging conflicting PRs.