Official ADM libraries for signing users in with the identity
providers most applications offer. The protocols (OAuth 2.0, OpenID Connect, JOSE) are in
std.proto.auth; each library here knows one provider: its endpoints, scopes, credential
format, the quirks of its tokens, and where its profile data comes from. They are written in
ADM, published as adm.auth.<provider> and signed by the admlang publisher, and live outside
the standard library because providers change these details without notice.
| Library | Provider | Protocol | Notes |
|---|---|---|---|
adm.auth.google |
OpenID Connect | ID tokens from One Tap and mobile apps verified too; Workspace domain checks | |
adm.auth.github |
GitHub | OAuth 2.0 | no OpenID Connect: the profile comes from the user and emails API; device flow; GitHub Apps |
adm.auth.microsoft |
Microsoft (Entra ID) | OpenID Connect | tenants, per-tenant issuers, certificates as client credentials, Microsoft Graph |
adm.auth.apple |
Apple | OpenID Connect | the client secret is a JWT the library signs and renews; the name arrives once |
Each library is a Provider built from the application's client id and credential.
start begins a sign-in (PKCE, state and, for OpenID Connect, a nonce always on) and
returns the request to keep with the session; exchange finishes it from the callback and
returns std.proto.auth.openid's Login: the tokens, the ID token and its claims, and a
Profile read the same way for every provider (id, email, emailVerified, name,
picture, locale, and the provider's raw claims). refresh renews the tokens. Every
Provider is an openid.SignInProvider, so a program that offers several providers writes one
callback handler and gives it the provider by name:
use std.proto.auth.openid
let providers = map<string, openid.SignInProvider>{"google": google, "github": github, "microsoft": microsoft}
let request = try providers[name].start()
// send the browser to request.url; at the callback:
let login = try providers[name].exchange(request, callbackURL)
print("{login.profile.name} <{login.profile.email}>")
Failures are oauth2.OAuthError, with the provider's error code and a kind.
Each suite runs against a loopback provider, so adm test needs no account. Signing in for
real needs a browser, so the suites verify real tokens only when given one:
ADM_TEST_GOOGLE_ID_TOKEN=... adm test auth/google