Skip to content

Conversation

@ahus1
Copy link
Contributor

@ahus1 ahus1 commented Sep 24, 2025

Closes #42922

This can be manually validated in one of the two following ways - I actually don't know how I would automatically test this, please share ideas if you could think of some.

  • Go to the Admin UI clients menu, and then access "Initial access token". Even selecting an entry would invalidate the cache previously. Now it wouldn't do that any more.

OR

You then look that no Realm invalidations are created in the debugger at

@ahus1 ahus1 self-assigned this Sep 24, 2025
@ahus1
Copy link
Contributor Author

ahus1 commented Sep 24, 2025

@pruivo - do you feel confident enough to review this PR, assuming that you haven't worked with client invalidation before?

Copy link
Member

@pruivo pruivo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. If I didn't miss anything, it does not interact with any cached data.

Whether those methods belong to RealModel is another story :) They exist in RealmProvider, and all invocations appear to be directed here.

@ahus1 ahus1 marked this pull request as ready for review September 24, 2025 19:31
@ahus1 ahus1 requested review from a team as code owners September 24, 2025 19:31
@ahus1 ahus1 merged commit a84d243 into keycloak:main Sep 24, 2025
78 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dynamic Client Registration invalidates the realm cache

2 participants