OidcTenantConfig

[LiuBo-keep]

I configured each tenant's OidcTenantConfig information on the page and stored it in the database. I used the TenantConfigResolver interface to retrieve tenant information and initialize OidcTenantConfig on each request. However, I've noticed that when I modify tenant information while the project is running, the changes in the OidcTenantConfig context are no longer effective, and the previous information remains. How can I ensure that changes to tenant information on the page take effect on the next request without restarting the service?

[sberyozkin]

@LiuBo-keep I believe we addressed it with #48278. It should work as expected starting from 3.24.0.
Note that modifying an instance of OidcTenantConfig in TenantConfigResolver directly is not effective and is also not thread safe.

See https://quarkus.io/guides/security-openid-connect-multitenancy#update-resolved-dynamic-tenant-configuration