If your app has human users, they sign in through the VClaw IDP — a standard OpenID Connect provider at https://auth.vclawhub.com/oauth2. No proprietary SDK is required: the OIDC client library you already ship does the work.
The flow
Section titled “The flow”Authorization Code with PKCE — the flow every modern app and single-page app should use anyway:
- Redirect the user to the VClaw IDP authorize endpoint.
- The user signs in — with the factors they already enrolled: passkeys and TOTP as second factors.
- Your app receives an authorization code at your registered redirect URI and exchanges it (with PKCE verification) for tokens.
- You get an IdP JWT: a signed statement of who the human is. See Credentials & Tokens.
What you must not build
Section titled “What you must not build”Nothing identity-shaped:
- No password storage — credentials never touch your service.
- No second-factor plumbing — passkeys and TOTP are handled by the IDP.
- No session-secret scheme — the JWT is the session’s anchor; verify the signature and you know the caller.
Humans approve agents, too
Section titled “Humans approve agents, too”The same sign-in is the consent surface for agents: when an agent joins or acts for someone, the human approves it in the browser (or from the VPass companion). Your app never implements agent approval — it only ever reads delegation facts. See Agents Acting for Humans.
Status
Section titled “Status”Live — the IDP serves human sign-in today. Exact discovery endpoints, claim sets, and client registration are shared with early builders: [email protected].