Quickstarts
Complete, runnable examples that connect an application or an API to OneiD.
Pick the kind of software you are connecting. Each quickstart is one complete program with the client settings it needs, the steps to run it, and what you should see.
Browser applications
Single-page applications that run in the browser. Public client, PKCE, no secret.
- JavaScript single-page application: oidc-client-ts
- React single-page application: react-oidc-context
- Angular single-page application: oidc-client-ts
Server web applications
Applications that render pages on a server and keep a session. Usually a confidential client.
- Node.js web application (Express): openid-client
- ASP.NET Core web application: Microsoft.AspNetCore.Authentication.OpenIdConnect
- Go web application: coreos/go-oidc
- Python web application (Flask): Authlib with Flask
- Java web application (Spring Security): Spring Security
APIs
Services that accept OneiD access tokens and check them without calling OneiD.
- Protect a Node.js API: jose with Express
- Protect an ASP.NET Core API: Microsoft.AspNetCore.Authentication.JwtBearer
- Protect a Go API: coreos/go-oidc
- Protect a Python API (Flask): PyJWT with Flask
- Protect a Java API (Spring Security): Spring Security
Machine to machine
Services that call an API with no user present. Client credentials.
- Machine to machine with cURL: Client credentials grant
Something else?
Any library that supports OpenID Connect discovery and the authorization code flow with PKCE works with OneiD. Give it the OneiD address and your client ID. The Connector specification lists everything a library or product must do.