Quarkus Security architecture
The Quarkus Security architecture provides several built-in authentication mechanisms and is highly customizable.
The primary mechanism for securing HTTP applications in Quarkus is the
When a client sends an HTTP request, Quarkus Security orchestrates security authentication and authorization by interacting with several built-in core components including
The sequential security validation process results in one of three outcomes:
The HTTP request gets authenticated and authorized and access to the Quarkus application gets granted.
The HTTP request authentication fails and the requester receives a challenge specific to the authentication mechanism, for example, a
401error, a URL redirect to reauthenticate, or some other custom authentication challenge response. For some practical examples of challenge responses, see the Quarkus Security Tips and Tricks guide.
The HTTP request authorization fails and the requester gets denied access to the Quarkus application.
The following diagram steps through the detailed process flow of the Quarkus Security architecture:
Quarkus Security uses
HttpAuthenticationMechanism to extract the authentication credentials from the HTTP request and delegates them to
IdentityProvider to convert the credentials to
For example, the credentials can come from the
Authorization header, client HTTPS certificates, or cookies.
When an authentication request is rejected by Quarkus Security,
HttpAuthenticationMechanism sends an authentication challenge back to the client.
The type of challenge depends on the authentication mechanism.
For example, with the OIDC OpenID Connect (OIDC) Authorization Code Flow mechanism, a redirect URL gets generated and the client is sent back to the OpenID Connect provider to authenticate.
IdentityProvider verifies the authentication credentials and maps them to
SecurityIdentity, which has the username, roles, original authentication credentials, and other attributes.
You can inject a
SecurityIdentity instance for every authenticated resource to get the authenticated identity information.
In other contexts, it is possible to have other parallel representations of the same information or parts of it, for example,
SecurityContext for Jakarta REST or
JsonWebToken for JSON Web Tokens (JWT).
For more information, see the Quarkus Identity providers guide.
Because Quarkus Security is customizable, for example, you can add authorization roles to
SecurityIdentity, you can register and prioritize one or more custom security augmentors.
Registered instances of
SecurityIdentityAugmentor are invoked during the final stage of the security authentication process.
For more information, see the Security Identity Customization section of the "Security Tips and Tricks" guide.
To learn more about security authentication in Quarkus and the supported mechanisms and protocols, see the Quarkus Authentication mechanisms in Quarkus guide.
Proactive authentication is enabled in Quarkus by default. The request is always authenticated if an incoming request has a credential, even if the target page does not require authentication. For more information, see the Quarkus Proactive authentication guide.
Quarkus Security is also highly customizable. You can customize the following core security components of Quarkus:
For more information about customizing Quarkus Security, including reactive security and how to register a security provider, see the Quarkus Security tips and tricks guide.