Description

quarkus-oidc has well over 100 properties, probably reaching 130 or so, which is currently duplicated by the identical tenant configuration, with the total number of generated properties now reaching 240 or so properties.

We can get rid of the duplication eventually, once #39185 is resolved , with the transition to @ConfigMapping, with Roberto advising how to add a few annotations to that mapping to cut the tenant duplications.

Let's say now we are back to 120-130 properties. Each of these properties has a goal:

• OIDC provider configuration (discovery related, non-discovery)
• TLS
• HTTP Proxy
• A ton of OIDC client authentication options, all of which are known to have been used
• session managemet
• logout managemet
• token verification management
• introspection, userinfo
• etc etc etc

However, when users look at the generated list of properties then can be overwhelmed and confused, once they need to go beyond the OIDC basics.

So there must be a new expanded configuration guide added, clearly grouping them, explaining their roles, possible useful combinations, etc.

Along the way, we can review, which of the properties can be set to stricter initial values.

CC @maxandersen @cescoffier

Implementation ideas

No response