We are using a single Quarkus instance to serve multiple user groups (ADMIN and USER). Up to now we were using one single authentication service so secure our web endpoints (configured in application.properties). Now requirements changed and we have to authenticate the USER endpoints with a different AS.
Does anybody have an hint how to do this in a simple way. My expectation would be to have some Quarkus config in application.properties like
# user authorisation (default, well documented at Quarkus)
quarkus.oidc.auth-server-url=https://url/to/user-auth
(...)
quarkus.http.auth.permission.app.paths=/admin/*
# admin authorisation (my guess)
quarkus.oidc.ADMIN.auth-server-url=https://url/to/admin-auth
(...)
quarkus.http.ADMIN.auth.permission.app.paths=/admin/*
I know best practice would be to create different service instances but we would like to safe the efforts duplicating the infrastructure and keep things in a single block.