Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamic Keycloak Policy Enforcer for multi-tenancy #25774

Closed
ansonquarkus opened this issue May 25, 2022 · 3 comments · Fixed by #39643
Closed

Dynamic Keycloak Policy Enforcer for multi-tenancy #25774

ansonquarkus opened this issue May 25, 2022 · 3 comments · Fixed by #39643

Comments

@ansonquarkus
Copy link

Description

Support creating keycloak authorization policy dynamically

Implementation ideas

No response

@ansonquarkus ansonquarkus added the kind/enhancement New feature or request label May 25, 2022
@quarkus-bot
Copy link

quarkus-bot bot commented May 25, 2022

/cc @pedroigor, @sberyozkin

@albert0815
Copy link

Hi @sberyozkin,

I am currently planning to create a multi tenant application with dynamic tenants. Using the OIDC TenantConfigResolver works to configure the tenants for authentication. Based on the documentation and this issue I assume that nothing similar exists for the authorisation using policy enforcer. Is there any plan to also build a dynamic solution for the policy enforcer? And maybe you could help recommending how to deal with this in the meantime.

Thanks

@michalvavrik
Copy link
Member

#39643 makes it possible through alternative and priority CDI annotations, though I would strongly encourage you to stick with dynamic tenant config resolution as I find it more practical.

@quarkus-bot quarkus-bot bot added this to the 3.14 - main milestone Jul 20, 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 a pull request may close this issue.

4 participants