Person administration

Review authority deliberately.

Sign in to inspect Delegations, review audit activity, and approve OAuth access for trusted Clients.

Open Dashboard

Runtime setup

Configure OAuth

  1. Deploy Runtime at a direct public HTTPS origin and set PDE_RUNTIME__BASE_URL to that exact origin.
  2. Keep PDE_RUNTIME__COOKIE_SECURE=true and set a unique, high-entropy PDE_RUNTIME__OWNER_SECRET. Never publish the secret, browser cookies, authorization codes, or access tokens.
  3. Start the Client's OAuth connection, then review its Client name, Client ID, redirect URI, protected resource, and scope on the consent page.
  4. Approving a trusted Client connects it to the Embassy but grants no Desk authority. Configure its access deliberately in Dashboard after OAuth completes.

Runtime configuration

Configure the application

Set these environment variables before starting Runtime. Values not listed as required use the shown defaults.

Variable Default Purpose and constraints
PDE_RUNTIME__BASE_URL Required Public Runtime origin, for example https://pde.example. It must be an absolute HTTP(S) origin without a path, query, fragment, or credentials. Use HTTPS outside explicit development.
PDE_RUNTIME__OWNER_SECRET Required Person login secret. Generate an independent value of at least 32 characters and keep it private.
PDE_RUNTIME__COOKIE_SECURE true for an HTTPS base URL; false for HTTP Marks Person session cookies as HTTPS-only. HTTPS deployments must use true. Accepted explicit values are true, false, 1, and 0.
PDE_RUNTIME__OWNER_SESSION_TTL_SECONDS 3600 Person session lifetime in seconds (one hour). Must be a positive integer.
PDE_RUNTIME__AUTHORIZATION_REQUEST_TTL_SECONDS 300 OAuth approval-request lifetime in seconds (five minutes). Must be a positive integer.
PDE_RUNTIME__AUTHORIZATION_CODE_TTL_SECONDS 120 OAuth authorization-code lifetime in seconds (two minutes). Must be a positive integer.
PDE_RUNTIME__ACCESS_TOKEN_TTL_SECONDS 900 OAuth access-token lifetime in seconds (15 minutes). Must be a positive integer.
PDE_RUNTIME__TRUSTED_CLIENTS_JSON {} Optional JSON object keyed by Client ID with trusted Client Metadata Documents. Leave empty to discover Client metadata over HTTPS during OAuth authorization.

Client connection

Connect an MCP Client

  1. Configure the Client with this exact MCP endpoint: Loading endpoint…
  2. The Client discovers the OAuth endpoints automatically, then completes authorization code flow with S256 PKCE in the Person's browser.
  3. Approval connects the Client but creates no Delegations.
  4. Configure an exposed Capability in Dashboard. Revoking its Delegation denies subsequent calls immediately.