I don't see much documentation about migrating SPI implementations including building, deploying, configuration, etc. with the Quarkus distribution.

Also some of our SPI properties are currently read from the environment like AWS region, SQS queue URL, etc. Can those still be read outside of the build step?

I don't see much documentation about migrating SPI implementations including building, deploying, configuration, etc. with the Quarkus distribution.

The only reference we have is https://www.keycloak.org/migration/migrating-to-quarkus. You can check there a little information about the differences when building/deploying.

In regards to configuration, I'm updating docs for now here keycloak/keycloak-documentation#1408.

But I think we should come up with a less verbose configuration when enabling a specific proxy vendor. For instance, we could have:

proxy-vendor=haproxy|apache|nginx

To automatically configure the server for a specific proxy vendor.

Perhaps we should also update our Proxy Guide with the information you are requesting.

@DGuhr What do you think?

@pedroigor I would like the documentation of reverse proxy setup around mtls to be moved to the new guides for Quarkus, and not exist in the server admin guides, as it's about configuring the server. +1 with introducing a high-level option around this, not sure about proxy-vendor, it conflicts a bit with db=vendor, and maybe it should be limited to just mtls since that's what it's doing? Haven't looked at the difference and if it really needs to be haproxy/haproxy/ngingx or should instead be something more generic on how to load cert info.

perhaps sth like proxy-mtls-conf=... or proxy-x509-default-mtls-conf=... ? Not sure either. A generic solution would be better for sure, haven't looked into the details, yet.