Do not expose Admin endpoints and Admin Console with Quarkus

Getting advice
1

Hi everyone,
I am in the process of migrating from Keycloak 15 (Wildfly) to (Quarkus). I have solved most of the configuration problems encountered, also regarding the custom SPI.
However, I am currently at the security stage of the admin panel. In Wildfly distro - I implemented the solution that is described here: Admin endpoints and Admin Console and additionally appropriate redirections on the HTTP based on IP.
I can not find a similar solution in the Quarkus distro (v18). Is there something like that or only about the restrictions on the HTTP server?

1 Like
2

For what it’s worth, potentially via the HTTP Apache IP rules. Blocked externally. Accessible from allowed IP address sets.

3

I am currently running into the same problem while upgrading from KC 15 to 19. A solution would be much appreciated.