Skip to main content
Every Jabrod product signs people in through one authorization server, Jabrod Accounts, at https://auth.jabrod.com. It implements OAuth 2.1 and OpenID Connect. Passwords are only ever typed on its sign-in page, auth.jabrod.com/sign-in. The products and their APIs stay where they are: jabrod.com, art.jabrod.com, and the MCP servers at https://jabrod.com/api/mcp/<product>.

Endpoints

Read endpoints from the discovery document rather than hard-coding them.

Rules

  • Authorization code with PKCE (S256) for every client. There is no implicit or password grant.
  • Codes last 60 seconds and work once.
  • Refresh tokens rotate on every use. Using an old one again ends the session.
  • Redirect URIs must match exactly. Loopback redirects for native apps and MCP clients match on any port.
  • The authorize response carries iss (RFC 9207).
  • prompt accepts none, login and consent.

Scopes

Tokens

  • Access tokens are ES256 JWTs (typ: at+jwt) that last one hour. Their aud is the product’s API, https://jabrod.com/api/<product>, or the MCP server URL the client asked for with resource.
  • ID tokens are signed with ES256. Claims: sub, email, email_verified, name, picture, sid.
  • Verify tokens with the keys at https://auth.jabrod.com/oauth/jwks.json, and check that iss is https://auth.jabrod.com.

By product

MCP clients

Each remote MCP server, https://jabrod.com/api/mcp/<product>, is an OAuth protected resource. This follows the MCP authorization spec:
  1. A client with no token gets 401 with:
  2. That metadata names https://auth.jabrod.com as the authorization server. The client reads its discovery document, registers itself (a Client ID Metadata Document, or POST https://auth.jabrod.com/oauth/register), and opens https://auth.jabrod.com/oauth/authorize with resource=https://jabrod.com/api/mcp/<product>.
  3. You sign in if you need to, and see a consent screen once, asking whether the app may use your Jabrod account. The client gets a token for that one server.
Personal API keys from jabrod.com/app/keys still work for clients that can’t sign in, and for CI.

Signing out everywhere

auth.jabrod.com/account lists the apps and devices signed in to your account. Sign out everywhere also signs out JBD on every computer and every MCP app. jabrod.com/account redirects there.