8000 Way to store and query composite roles · Issue #11844 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Way to store and query composite roles #11844

Closed

Description

@vramik

#11816 (comment)

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.

to explore

Activity

  1. added
    area/storageStorage layer — JPA entities, database schemas, Liquibase migrations, caching
    on May 5, 2022
  2. changed the title [-]A way how to store and query composite roles[/-] [+]Way to store and query composite roles[/+] on Jun 20, 2022
  3. ahus1 commented on Jun 28, 2022

    @ahus1
    Member

    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

  4. self-assigned this
    on Jun 28, 2022
  5. added a commit that references this issue on Jul 1, 2022
    9143d8b
  6. Repository owner moved this from 📤 Todo to ✅ Done in Storageon Jul 1, 2022
  7. ahus1 commented on Jul 4, 2022

    @ahus1
    Member

    Follow-up issue with the remaining tasks: #12888

  8. added this to the 19.0.0 milestone on Aug 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/storageStorage layer — JPA entities, database schemas, Liquibase migrations, caching

Type

No type

Fields

No fields configured for issues without a type.

Projects

  • Status
    ✅ Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

0