Your use case
You manage users and authentication in a new or existing system, and need to issue tokens to other applications. You choose to own the authorization service and its maintenance.
Experimental · Community-maintained
A Quarkus extension for experienced teams building and maintaining their own OAuth 2.0 authorization service, with optional OpenID Connect. For new or existing systems.
Maintained by community contributors, not by the Quarkus project or team.
1.0.0-beta2Experimental extension for Quarkus
curl -u machine-client:machine-secret \
-d grant_type=client_credentials \
-d scope=message.read \
http://127.0.0.1:8080/oauth2/token{
"access_token": "eyJ…",
"token_type": "Bearer",
"expires_in": 120
}Protocol endpoints built with Quarkus
This project is for deliberate authorization-server development. For application login or API protection, start with an established OAuth/OIDC provider and Quarkus Security.
You manage users and authentication in a new or existing system, and need to issue tokens to other applications. You choose to own the authorization service and its maintenance.
OAuth protocol endpoints, client authentication, consent and token issuance. Optional OpenID Connect adds provider capabilities for client sign-in.
User authentication, access policies, durable storage, keys and deployment. Your team evaluates protocol behavior, reviews security and operates the service.
Learn the setup, look up the details, then explore the flow.
Start the server, get a token, and learn how authorization fits into your application.
Read the guides→Look up configuration, defaults and extension points. Check protocol boundaries and supported customization points.
Open the reference→Try four OAuth flows, inspect tokens and call protected APIs. PKCE, JWT and request tools are also available offline.
Open the Playground→