Support for backchannel logout for dynamic clients

[calvernaz]

Please add support for backchannel logout for dynamic clients.

I tracked back to this PR why this is not supported so I'm not sure it's easy to dynamically create vertx routes. But this feature would be very welcome.

quarkus/extensions/oidc/runtime/src/main/java/io/quarkus/oidc/runtime/TenantContextFactory.java

Line 82 in a22604a

if (oidcConfig.logout().backchannel().path().isPresent()) {

[quarkus-bot]

/cc @pedroigor (bearer-token,oidc)

[sberyozkin]

That will probably require some convention allowing for a single route handler to handle all requests starting from some common root path like /backchannel/ and then the tenant-id subpath, say, /backchannel/dynamic-tenant-1, etc...

[calvernaz]

Could the prefix be sourced from the root path, or a new configuration?

[sberyozkin]

Yeah, we have a back channel path tenant property. We should be able to use a single route handler.

Some thinking will be needed as right now, each tenant may have its own back-channel cache property, that may have to be deprecated, to support a single back-channel cache for all tenants... We'll see a bit later how it can work out

[kpagratis]

Will this end up in the 3.20 LTS branch?