> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jabrod.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign in with Jabrod (OAuth)

> One OAuth 2.1 and OpenID Connect server for every Jabrod product.

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

| | |
| - | - |
| Issuer | `https://auth.jabrod.com` |
| Discovery | `https://auth.jabrod.com/.well-known/openid-configuration`, also `/.well-known/oauth-authorization-server`. `https://jabrod.com/.well-known/oauth-authorization-server` returns the same document. |
| Authorize | `https://auth.jabrod.com/oauth/authorize` |
| Token | `POST https://auth.jabrod.com/oauth/token` (form-encoded or JSON) |
| Revoke | `POST https://auth.jabrod.com/oauth/revoke` (RFC 7009) |
| UserInfo | `https://auth.jabrod.com/oauth/userinfo` (needs the `openid` scope) |
| JWKS | `https://auth.jabrod.com/oauth/jwks.json` (ES256) |
| Register | `POST https://auth.jabrod.com/oauth/register` (MCP clients only, RFC 7591) |
| Sign out | `https://auth.jabrod.com/oauth/logout?post_logout_redirect_uri=…` |

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

| Scope | Gives |
| - | - |
| `openid` | An ID token and UserInfo |
| `profile`, `email` | Name, picture and email address |
| `offline_access` | A refresh token |
| `art`, `context`, `evals`, `signals`, `jbd` | Access to that product |

## 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

| Product | How it signs you in |
| - | - |
| jabrod.com (`/app/context`, `/app/evals`, `/app/signals`, `/app/keys`) | jabrod.com is a client of auth.jabrod.com. Its **Sign in** sends you to auth.jabrod.com and back. |
| art.jabrod.com and Art Studio | Also a client of auth.jabrod.com, with its own session on the art host. |
| JBD | Its browser sign-in now opens `auth.jabrod.com/desktop/authorize`. `jabrod.com/desktop/authorize` redirects there, so installed versions keep working. See [Your Jabrod account](https://docs.jabrod.com/platform/account.md#sign-in-from-jbd). |
| MCP clients | Sign in from the client, as below. |
| docs.jabrod.com | Needs no sign-in. |

## 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:

   ```http theme={null}
   WWW-Authenticate: Bearer resource_metadata="https://jabrod.com/.well-known/oauth-protected-resource/api/mcp/context", scope="context"
   ```

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](https://jabrod.com/app/keys) still work for clients that can't sign in, and for CI.

## Signing out everywhere

[auth.jabrod.com/account](https://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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.