Skip to main content
Once you have worked through the OAuth 2.0 and OpenID Connect tutorials, the next step is to see Authlete working inside an actual authorization server. Authlete is the backend that handles the OAuth 2.0 and OpenID Connect protocol logic — it does not expose endpoints to clients or end users directly. To run real flows end to end, you pair it with an authorization server frontend that calls the Authlete APIs. To make this easy to try, Authlete publishes runnable sample servers that you can deploy and exercise against your own service.

​
Java

The Java reference implementation, java-oauth-server, is a full-featured authorization server. Beyond the basic OAuth 2.0 / OpenID Connect flows, it supports advanced specifications including FAPI (1.0 and 2.0), OpenID Federation, and OpenID for Verifiable Credential Issuance (OID4VCI), as well as CIBA (Client-Initiated Backchannel Authentication), the OAuth 2.0 Device Authorization Grant (Device Flow), Pushed Authorization Requests (PAR), Grant Management, and Dynamic Client Registration. To set it up and run OAuth 2.0 / OpenID Connect flows against it, see Using Demo Authorization Server.

​
Other languages

Sample servers for other languages are planned, and will be listed here as they become available.