The following update was added to the Known Issue section of the Release Notes version 3.2.9.SP1:  https://docs.google.com/document/d/18UeVebhLomwkrSuiTNL_SalonVbdCBuS1ODiQXujg-8/edit  

This issue is also relevant for 3.8, however, a different workaround is available.

Draft discussions with SME: https://docs.google.com/document/d/1DruitND3pWIv0WVN51vqqd6q84RfWpqKIGPsu9Y03wY/edit?usp=sharing 

Comment from Sergey: instead of suggesting a quarkus.oidc.TenantResolver workaround, a new @quarkus.oidc.Tenant annotation solution should be recommended. The note will be exactly as the 3.2.9.SP1/2.13.9.SP1, except that the The workaround is to use quarkus.oidc.TenantResolver to resolve the current OIDC configuration tenant id can be replaced with something like From now on use a quarkus.oidc.Tenant annotation

SME: Sergey