An authentication policy determines whether requests to a resource collection must be associated with an authenticated identity. In Quarkus, define a collection of paths and assign it a policy; applying `authenticated` to `/*` forbids anonymous access to every exposed resource. section 6.1.2
Listing 6.3 Security-related configuration in the Users service
quarkus.http.auth.permission.all-resources.paths=/* quarkus.http.auth.permission.all-resources.policy=authenticated quarkus.oidc.application-type=web_app quarkus.oidc.logout.path=/logout
Use this configuration to protect all Users service resources and enable browser-oriented OIDC login and logout. section 6.1.2
Configure the policy by:
- Choosing the resource paths, such as `/*` for the entire application. section 6.1.2
- Assigning `authenticated`, or using a more fine-grained policy such as a required role. section 6.1.2
- Selecting `web_app` for browser redirects through the Authorization Code Flow; use `service` for REST resources that authenticate with an Authorization header. section 6.1.2
- Adding a logout path to invalidate the active session. section 6.1.2
