Add Keycloak Authorization dynamic tenant config resolution

[michalvavrik]

• Closes: Dynamic Keycloak Policy Enforcer for multi-tenancy #25774
• Closes: Support the dynamic KeycloakPolicyEnforcerAuthorizer tenants #17664

[github-actions]

🙈 The PR is closed and the preview is expired.

[michalvavrik]

hey @pedroigor please review if you would like, otherwise in terms of what is changed, changes are not specific to Keycloak (it's a CDI feature...), so @sberyozkin is right reviewer for this.

[michalvavrik]

@sberyozkin I pushed it by accident as I need to fix some tests, docs and write more tests, but as it's already there, you can look at the builder and provide early feedback. Or not. Anyway, it's as compact as I could make it. Cheers.

[michalvavrik]

Done, the DynamicTenantConfigPolicyEnforcerTest tests new builder comprehensively.

[sberyozkin]

Hi @michalvavrik, can you please type a builder sequence showing all the supported properties being set, I was not sure about setGet("write")...

[michalvavrik]

ping @sberyozkin

[michalvavrik]

I've rebased on the current main and resolved merge conflicts just in case @sberyozkin find a time to review.

[michalvavrik]

@sberyozkin please have a look; I won't resolve merge conflicts again as I'm bit worried it's wasting of CI resources. Will do it when you find a time for this

[michalvavrik]

Merge conflicts were about TLS registry, the rest of this PR still applies. Resolved.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 24aef29.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

You can consult the Develocity build scans.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 24aef29.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

[sberyozkin]

Thanks @michalvavrik , let's do it and start planning doing something similar for OIDC 🙂
Cheers Sergey