Skip to content

Conversation

@shawkins
Copy link
Contributor

@shawkins shawkins commented Oct 22, 2024

closes: #34095

An alternative here was to expand the KeycloakSession logic so that it can return a new, not cached, provider instance. However I thought that this usage of system properties should be a special case and decided against it.

Copy link
Contributor

@vmuzikar vmuzikar left a comment

Choose a reason for hiding this comment

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

@shawkins LGTM, thank you.

We should really get rid of configuring the import/export providers via sys props eventually.

Can you please create a backport?

@vmuzikar vmuzikar merged commit bd49975 into keycloak:main Oct 23, 2024
shawkins added a commit to shawkins/keycloak that referenced this pull request Oct 23, 2024
closes: keycloak#34095

Signed-off-by: Steve Hawkins <[email protected]>
(cherry picked from commit bd49975)
@shawkins
Copy link
Contributor Author

We should really get rid of configuring the import/export providers via sys props eventually.

Absolutely. I would have liked to do that, but it's quite a change. As far as I can see the lifecycle of the provider factory and provider aren't designed well for this. An option would be to put config overrides on the KeycloakContext (and reference that in the provider, rather than System.getxxx) - when those are present, we'd also have to use them as part of the cache keys with further changes along the lines of #34220

Can you please create a backport?

#34252

vmuzikar pushed a commit that referenced this pull request Oct 23, 2024
closes: #34095

Signed-off-by: Steve Hawkins <[email protected]>
(cherry picked from commit bd49975)
@edewit edewit mentioned this pull request Nov 19, 2024
@edewit edewit mentioned this pull request Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Keycloak 26.0.0/26.0.1 Import Issue: Multiple Realms Not Imported, Duplicated Realm Imported Instead

2 participants