Sign in with AutonomousRelay lets people sign in to your app with their AutonomousRelay account. It is standard OpenID Connect (the authorization code flow with PKCE), so any OpenID Connect library works. Your app learns who the person is and, if they agree, which organisation they belong to and their role in it.
Step 1: Register your app
In Sign-in apps, select Register an app and fill in:
- Name: shown on the sign-in screen, with your organisation’s name beneath it. Up to 60 characters.
- Kind of app: a server app keeps a client secret on a server; a browser or mobile app cannot keep one and signs in with PKCE alone. This cannot be changed later.
- Redirect URIs: up to 10, matched exactly, with no wildcards.
httpsonly, excepthttp://localhostandhttp://127.0.0.1on any port, for development. - Homepage, Logo URL and Privacy policy: optional to start, required for review.
You get a client ID (arc_…, public) and, for a server app, a client secret (arcs_…). The secret is shown once: we keep only a hash of it. New secret makes another, and the old one keeps working for 24 hours so you can deploy the new one first.
Step 2: Point your library at us
Configure your OpenID Connect library with:
- Issuer:
https://autonomousrelay.com - Discovery:
https://autonomousrelay.com/.well-known/openid-configuration - Your client ID, and for a server app the secret. The token endpoint accepts it as HTTP Basic (
client_secret_basic) or in the form (client_secret_post); a browser or mobile app sends onlyclient_id(none).
Most libraries read everything else from discovery. For reference, the endpoints are:
- Authorization:
https://autonomousrelay.com/auth - Token:
https://autonomousrelay.com/v1/oauth/token - Userinfo:
https://autonomousrelay.com/v1/oauth/userinfo - Revocation:
https://autonomousrelay.com/v1/oauth/revoke - Signing keys:
https://autonomousrelay.com/v1/oauth/jwks
Step 3: Send people to sign in
Redirect the browser to the authorization endpoint:
GET https://autonomousrelay.com/auth ?response_type=code &client_id=arc_YOUR_CLIENT_ID &redirect_uri=https://app.example.com/callback &scope=openid email profile org &state=RANDOM_STATE &nonce=RANDOM_NONCE &code_challenge=BASE64URL_SHA256_OF_VERIFIER &code_challenge_method=S256
state,nonceand PKCE (code_challenge_method=S256) are required, for server apps too.promptmay benone,login,consentorselect_account, andmax_ageandlogin_hintare supported.- With
prompt=none, a person who is not signed in, or has not approved your app, comes back witherror=login_requiredorerror=consent_required.
The person sees what your app will receive and chooses whether to continue. If they approved it before for the same scopes, and your app’s name and logo have not changed, they go straight through. They come back to your redirect URI with code, your state and iss. Check that state is yours and iss is https://autonomousrelay.com.
Step 4: Exchange the code
The code works once, for 60 seconds:
curl -sS -X POST https://autonomousrelay.com/v1/oauth/token \ -u "$CLIENT_ID:$CLIENT_SECRET" \ -d grant_type=authorization_code \ -d code="$CODE" \ -d redirect_uri=https://app.example.com/callback \ -d code_verifier="$VERIFIER"
{
"id_token": "eyJ...",
"access_token": "ar-oidc-...",
"token_type": "Bearer",
"expires_in": 300,
"refresh_token": "ar-rt-...",
"scope": "openid email profile org"
}Verify the id_token as your library does: signed with ES256 by a key from our JWKS, iss is https://autonomousrelay.com, aud is your client ID, it has not expired (it lasts 5 minutes), and nonce is the one you sent.
Scopes and claims
openid(required):sub, the person’s ID. It never changes; use it, not the email, as your account key. Alsoauth_timeandamr(fedfor Google or GitHub,ssofor the organisation’s identity provider,wallet).email:emailandemail_verified, only when the address is verified. Otherwise neither is sent.profile:nameandpicture, when the person has them.org: the organisation the person chooses on the sign-in screen:org_id,org_nameandorg_role(owner,adminormember).
The same claims are at the userinfo endpoint, with the access token as Authorization: Bearer. An access token lasts 5 minutes and works only there; it is refused on every other API route.
Refresh tokens
Every code exchange returns a refresh token. Trade it for fresh tokens:
curl -sS -X POST https://autonomousrelay.com/v1/oauth/token \ -u "$CLIENT_ID:$CLIENT_SECRET" \ -d grant_type=refresh_token \ -d refresh_token="$REFRESH_TOKEN"
- Each refresh returns a new refresh token; keep it and drop the old one. Using an old one again revokes the whole sign-in.
- A refresh token expires after 30 days unused, and a sign-in lasts at most 90 days from the start. Then the person signs in again.
- A refresh also re-checks the person: their organisation membership, role and name are current in the new ID token, which has no
nonce. 400invalid_grantmeans the sign-in is over (the person revoked your app, left the organisation, or the organisation blocked your app). Sign the person out of your app.
To sign someone out, revoke their refresh token at https://autonomousrelay.com/v1/oauth/revoke with token= and your client credentials. It answers 200 either way, and ends every token from that sign-in.
Review and the Verified badge
To let anyone with an AutonomousRelay account sign in, select Submit for review. The app needs a logo, a homepage and a privacy policy, and no localhost redirect URIs. Our staff check that your organisation is real, that the name and logo imitate no one, that the homepage and privacy policy load, and that every redirect URI is on a domain you control. A verified app shows a Verified badge on the sign-in screen.
If changes are requested, the note is on your Sign-in apps page; fix the app and submit it again. Changing a verified app’s name or logo, or adding a redirect URI on a new domain, sends it back to review by itself. Until that change is approved, people outside your organisation see the last verified name and logo and can use only the verified redirect URIs, so sign-ins keep working.
What people and organisations control
- A person sees every app they signed in to under Settings → Apps you signed in to, and can revoke one: its refresh tokens stop working at once and userinfo answers
401. - An Owner or Admin sees which apps members shared the organisation with, and how many members (never which), under Sign-in apps → Apps your members use. Blocking an app ends its access to the organisation at once.
- Disable on your app stops new sign-ins at once; Delete also ends codes already issued.