@openparachute/hub 0.5.7 → 0.5.9-rc.6

package/src/__tests__/module-manifest.test.ts

@@ -126,6 +126,54 @@ describe("validateModuleManifest", () => {
     ).toThrow(/http:.*https:/);
   });
 
+  test("uiUrl accepts a leading-slash path (Phase D)", () => {
+    const m = validateModuleManifest({ ...VALID, uiUrl: "/notes" }, "x");
+    expect(m.uiUrl).toBe("/notes");
+  });
+
+  test("uiUrl accepts an absolute https URL", () => {
+    const m = validateModuleManifest({ ...VALID, uiUrl: "https://app.example.com/" }, "x");
+    expect(m.uiUrl).toBe("https://app.example.com/");
+  });
+
+  test("uiUrl rejects empty / non-string / non-url-or-path (mirrors managementUrl)", () => {
+    expect(() => validateModuleManifest({ ...VALID, uiUrl: "" }, "x")).toThrow(/uiUrl/);
+    expect(() => validateModuleManifest({ ...VALID, uiUrl: 7 }, "x")).toThrow(/uiUrl/);
+    expect(() => validateModuleManifest({ ...VALID, uiUrl: "no-slash" }, "x")).toThrow(
+      /path starting with "\/" or a full http\(s\) URL/,
+    );
+    expect(() => validateModuleManifest({ ...VALID, uiUrl: "ftp://example.com" }, "x")).toThrow(
+      /http:.*https:/,
+    );
+  });
+
+  test("uiUrl absent stays absent", () => {
+    const m = validateModuleManifest(VALID, "x");
+    expect(m.uiUrl).toBeUndefined();
+  });
+
+  // Open-redirect regression: protocol-relative paths like "//evil.com" pass
+  // a naive `startsWith("/")` check but `new URL("//evil.com", base)` resolves
+  // to the foreign origin. A malicious third-party module could plant such a
+  // value in module.json:uiUrl and turn a discovery tile into an off-origin
+  // redirect. Both uiUrl and managementUrl are validated by the shared
+  // asPathOrUrl helper, so cover both.
+  test("uiUrl rejects protocol-relative paths (open-redirect regression)", () => {
+    expect(() => validateModuleManifest({ ...VALID, uiUrl: "//evil.com" }, "x")).toThrow(/uiUrl/);
+    expect(() => validateModuleManifest({ ...VALID, uiUrl: "//evil.com/path" }, "x")).toThrow(
+      /uiUrl/,
+    );
+  });
+
+  test("managementUrl rejects protocol-relative paths (open-redirect regression)", () => {
+    expect(() => validateModuleManifest({ ...VALID, managementUrl: "//evil.com" }, "x")).toThrow(
+      /managementUrl/,
+    );
+    expect(() =>
+      validateModuleManifest({ ...VALID, managementUrl: "//evil.com/admin" }, "x"),
+    ).toThrow(/managementUrl/);
+  });
+
   test("managementUrl absent stays absent", () => {
     const m = validateModuleManifest(VALID, "x");
     expect(m.managementUrl).toBeUndefined();

package/src/__tests__/oauth-handlers.test.ts

@@ -6,7 +6,7 @@ import { join } from "node:path";
 import { getClient, registerClient } from "../clients.ts";
 import { CSRF_COOKIE_NAME } from "../csrf.ts";
 import { hubDbPath, openHubDb } from "../hub-db.ts";
-import { validateAccessToken } from "../jwt-sign.ts";
+import { findTokenRowByJti, validateAccessToken } from "../jwt-sign.ts";
 import {
   authorizationServerMetadata,
   buildServicesCatalog,
@@ -1034,10 +1034,37 @@ describe("handleToken — full OAuth dance", () => {
 
       // closes #81 — services catalog tells the client where vault lives so
       // notes doesn't have to re-probe /.well-known/parachute.json. A
-      // vault:read token only sees the vault entry.
+      // `vault:default:read` token sees both the collapsed `vault` key
+      // (backwards compat) AND the per-vault `vault:default` key (closes
+      // #247 — pre-#247 only the collapsed key was emitted; consumers on
+      // multi-vault hubs were forced to assume `/vault/default` and
+      // collided).
       expect(tokenBody.services).toEqual({
         vault: { url: `${ISSUER}/vault/default`, version: "0.3.0" },
-      });
+        "vault:default": { url: `${ISSUER}/vault/default`, version: "0.3.0" },
+      });
+
+      // closes #215 reviewer F2 — Phase 1 code-grant access-token registry
+      // exemption pinning. The access token and refresh token share `jti`
+      // by design (signRefreshToken({ jti: access.jti, ... }) at the mint
+      // site), so the `tokens` row keyed by the access-token jti IS the
+      // shared row — refresh_token_hash is non-null, created_via is
+      // 'oauth_refresh'. We deliberately don't write a separate per-jti
+      // access-token row; revocation acts on the shared jti / family,
+      // bounded by the 15-min access TTL.
+      expect(payload.jti).toBeTruthy();
+      const row = findTokenRowByJti(db, payload.jti as string);
+      expect(row).not.toBeNull();
+      expect(row?.createdVia).toBe("oauth_refresh");
+      expect(row?.familyId).toBeTruthy();
+      // Verify the registry has exactly one row for this code-grant
+      // (not two — no separate access-token row).
+      const rowCount = (
+        db
+          .query<{ n: number }, [string]>("SELECT COUNT(*) as n FROM tokens WHERE jti = ?")
+          .get(payload.jti as string) ?? { n: 0 }
+      ).n;
+      expect(rowCount).toBe(1);
     } finally {
       cleanup();
     }
@@ -1523,6 +1550,156 @@ describe("handleToken — full OAuth dance", () => {
       vault: { url: `${ISSUER}/vault/work`, version: "0.3.0" },
     });
   });
+
+  // closes #247 — multi-vault correctness. Pre-#247 every vault collapsed
+  // under the single `vault` key, so Notes' OAuthCallback always wrote
+  // VaultRecord URL = paths[0] of the first vault row regardless of which
+  // vault the token actually granted. Per-vault `vault:<name>` keys let
+  // consumers route each grant to the correct vault URL.
+  describe("services catalog — multi-vault per-vault keys (#247)", () => {
+    // Real shape from a multi-vault hub: one `parachute-vault` row with N
+    // paths, each path naming an instance. Aaron's setup verbatim (4
+    // vaults: default, boulder, gitcoin, techne).
+    const multiVaultManifest: ServicesManifest = {
+      services: [
+        {
+          name: "parachute-vault",
+          port: 1940,
+          paths: ["/vault/default", "/vault/boulder", "/vault/gitcoin", "/vault/techne"],
+          health: "/health",
+          version: "0.4.4",
+        },
+      ],
+    };
+
+    test("single-vault hub with broad scope: only collapsed `vault` key (unchanged)", () => {
+      // Per-vault keys are noise on single-vault hubs — no disambiguation
+      // is needed. Backwards compat for pre-popover clients matters here.
+      expect(buildServicesCatalog(FIXTURE_MANIFEST, ISSUER, ["vault:read"])).toEqual({
+        vault: { url: `${ISSUER}/vault/default`, version: "0.3.0" },
+      });
+    });
+
+    test("single-vault hub with per-vault-narrowed scope: emits per-vault key too", () => {
+      // A `vault:default:read` token is an explicit consumer signal that
+      // the per-vault key matters — emit it even on a single-vault hub so
+      // the consumer's `services["vault:default"]` lookup works uniformly
+      // regardless of how many vaults the hub has.
+      expect(buildServicesCatalog(FIXTURE_MANIFEST, ISSUER, ["vault:default:read"])).toEqual({
+        vault: { url: `${ISSUER}/vault/default`, version: "0.3.0" },
+        "vault:default": { url: `${ISSUER}/vault/default`, version: "0.3.0" },
+      });
+    });
+
+    test("multi-vault hub with broad scope: emits every per-vault key + collapsed `vault`", () => {
+      // Broad `vault:read` admits every vault on the hub. Per-#247
+      // guidance: emit per-vault keys for all admitted vaults so the
+      // consumer (Notes popover) can pick its target by name without
+      // re-probing /.well-known/parachute.json.
+      expect(buildServicesCatalog(multiVaultManifest, ISSUER, ["vault:read"])).toEqual({
+        // Collapsed key still emitted (first admitted path); backwards compat.
+        vault: { url: `${ISSUER}/vault/default`, version: "0.4.4" },
+        "vault:default": { url: `${ISSUER}/vault/default`, version: "0.4.4" },
+        "vault:boulder": { url: `${ISSUER}/vault/boulder`, version: "0.4.4" },
+        "vault:gitcoin": { url: `${ISSUER}/vault/gitcoin`, version: "0.4.4" },
+        "vault:techne": { url: `${ISSUER}/vault/techne`, version: "0.4.4" },
+      });
+    });
+
+    test("multi-vault hub with per-vault scope: only that vault's per-vault key", () => {
+      // Aaron's "Connect boulder" flow: token has `vault:boulder:write`,
+      // scope admits only boulder. Pre-#247 the catalog said `vault.url =
+      // /vault/default` (WRONG), so Notes stored a /vault/default record
+      // with scope `vault:boulder:write` — collision city as more vaults
+      // got connected. Post-#247 the consumer reads
+      // `services["vault:boulder"].url` which correctly says /vault/boulder.
+      expect(buildServicesCatalog(multiVaultManifest, ISSUER, ["vault:boulder:write"])).toEqual({
+        // Collapsed `vault` points at boulder too — the only admitted
+        // vault — so legacy consumers happen to land on the right URL even
+        // though they have no per-vault awareness.
+        vault: { url: `${ISSUER}/vault/boulder`, version: "0.4.4" },
+        "vault:boulder": { url: `${ISSUER}/vault/boulder`, version: "0.4.4" },
+      });
+    });
+
+    test("multi-vault hub with mixed scopes: per-vault keys for each narrowed vault", () => {
+      // A token granting both `vault:boulder:read` and `vault:gitcoin:write`
+      // admits exactly those two vaults; default and techne aren't reachable.
+      expect(
+        buildServicesCatalog(multiVaultManifest, ISSUER, [
+          "vault:boulder:read",
+          "vault:gitcoin:write",
+        ]),
+      ).toEqual({
+        vault: { url: `${ISSUER}/vault/boulder`, version: "0.4.4" },
+        "vault:boulder": { url: `${ISSUER}/vault/boulder`, version: "0.4.4" },
+        "vault:gitcoin": { url: `${ISSUER}/vault/gitcoin`, version: "0.4.4" },
+      });
+    });
+
+    test("multi-vault hub: broad + per-vault scopes coexist; broad opens all vaults", () => {
+      // A token that carries BOTH `vault:read` (broad) AND
+      // `vault:boulder:write` (narrow) should land in the broad bucket
+      // because the broad scope is more permissive — narrowing one verb
+      // can't take away access the unnamed scope already granted.
+      expect(
+        buildServicesCatalog(multiVaultManifest, ISSUER, ["vault:read", "vault:boulder:write"]),
+      ).toEqual({
+        vault: { url: `${ISSUER}/vault/default`, version: "0.4.4" },
+        "vault:default": { url: `${ISSUER}/vault/default`, version: "0.4.4" },
+        "vault:boulder": { url: `${ISSUER}/vault/boulder`, version: "0.4.4" },
+        "vault:gitcoin": { url: `${ISSUER}/vault/gitcoin`, version: "0.4.4" },
+        "vault:techne": { url: `${ISSUER}/vault/techne`, version: "0.4.4" },
+      });
+    });
+
+    test("legacy per-vault rows (parachute-vault-<name>) also produce per-vault keys", () => {
+      // Older multi-vault layout — one row per vault — should produce the
+      // same catalog shape as the single-row-multi-path layout. The
+      // `vaultInstanceNameFor` helper handles both via its
+      // manifest-suffix fallback.
+      const legacyManifest: ServicesManifest = {
+        services: [
+          {
+            name: "parachute-vault",
+            port: 1940,
+            paths: ["/vault/default"],
+            health: "/health",
+            version: "0.4.4",
+          },
+          {
+            name: "parachute-vault-work",
+            port: 1941,
+            paths: ["/vault/work"],
+            health: "/health",
+            version: "0.4.4",
+          },
+        ],
+      };
+      expect(buildServicesCatalog(legacyManifest, ISSUER, ["vault:read"])).toEqual({
+        vault: { url: `${ISSUER}/vault/default`, version: "0.4.4" },
+        "vault:default": { url: `${ISSUER}/vault/default`, version: "0.4.4" },
+        "vault:work": { url: `${ISSUER}/vault/work`, version: "0.4.4" },
+      });
+    });
+
+    test("non-vault services unaffected — only one key per service, no per-instance variant", () => {
+      // The per-vault-key expansion is vault-specific. scribe / notes /
+      // third-party rows still emit one key per service.
+      expect(
+        buildServicesCatalog(FIXTURE_MANIFEST, ISSUER, [
+          "vault:default:read",
+          "scribe:transcribe",
+          "notes:read",
+        ]),
+      ).toEqual({
+        vault: { url: `${ISSUER}/vault/default`, version: "0.3.0" },
+        "vault:default": { url: `${ISSUER}/vault/default`, version: "0.3.0" },
+        scribe: { url: `${ISSUER}/scribe`, version: "0.3.0-rc.1" },
+        notes: { url: `${ISSUER}/notes`, version: "0.3.0" },
+      });
+    });
+  });
 });
 
 // closes #72 — RFC 6749 §3.2.1 + §2.3.1: confidential clients must
@@ -2054,6 +2231,76 @@ describe("DCR approval gate (#74)", () => {
       const html = await res.text();
       expect(html).toContain("App not yet approved");
       expect(html).toContain("approve-client");
+      // No vault hint → no vault row in approve-meta. Single-vault hubs +
+      // pre-vault-popover clients leave the section omitted (#244).
+      expect(html).not.toContain('approve-meta-label">vault');
+    } finally {
+      cleanup();
+    }
+  });
+
+  // closes #244 — vault hint surfaced in approve-pending UI. Notes#115
+  // passes `vault=<name>` on `/oauth/authorize` for per-vault grants; hub's
+  // approve page now displays it alongside the other client metadata so a
+  // multi-vault operator can tell which vault they're approving for.
+  test("authorize: pending client with vault hint → approve UI renders 'vault: <name>'", async () => {
+    const { db, cleanup } = await makeDb();
+    try {
+      const reg = registerClient(db, {
+        redirectUris: ["https://app.example/cb"],
+        status: "pending",
+      });
+      const { challenge } = makePkce();
+      const req = new Request(
+        authorizeUrl({
+          client_id: reg.client.clientId,
+          redirect_uri: "https://app.example/cb",
+          response_type: "code",
+          code_challenge: challenge,
+          code_challenge_method: "S256",
+          scope: "vault:read",
+          vault: "boulder",
+        }),
+      );
+      const res = handleAuthorizeGet(db, req, { issuer: ISSUER });
+      expect(res.status).toBe(403);
+      const html = await res.text();
+      expect(html).toContain("App not yet approved");
+      // The vault hint surfaces as a labeled row in the approve-meta block.
+      expect(html).toContain('approve-meta-label">vault');
+      expect(html).toContain("boulder");
+    } finally {
+      cleanup();
+    }
+  });
+
+  test("authorize: pending client with empty vault param → no vault row", async () => {
+    // Defensive: `vault=` with empty value normalizes to undefined so the
+    // UI doesn't render a blank vault label. Easy to hit if a client builds
+    // the URL via URLSearchParams.set("vault", someMaybeEmptyVar).
+    const { db, cleanup } = await makeDb();
+    try {
+      const reg = registerClient(db, {
+        redirectUris: ["https://app.example/cb"],
+        status: "pending",
+      });
+      const { challenge } = makePkce();
+      const req = new Request(
+        authorizeUrl({
+          client_id: reg.client.clientId,
+          redirect_uri: "https://app.example/cb",
+          response_type: "code",
+          code_challenge: challenge,
+          code_challenge_method: "S256",
+          scope: "vault:read",
+          vault: "",
+        }),
+      );
+      const res = handleAuthorizeGet(db, req, { issuer: ISSUER });
+      expect(res.status).toBe(403);
+      const html = await res.text();
+      expect(html).toContain("App not yet approved");
+      expect(html).not.toContain('approve-meta-label">vault');
     } finally {
       cleanup();
     }
@@ -2103,6 +2350,13 @@ describe("DCR approval gate (#74)", () => {
       const body = (await res.json()) as Record<string, unknown>;
       expect(body.error).toBe("invalid_client");
       expect(body.error_description).toContain("not been approved");
+      // Surface the inline-approval affordances so consumers (Notes, future
+      // cross-origin SPAs) can deep-link the operator to a browser-based
+      // approve flow without dropping to a terminal.
+      expect(body.approve_url).toBe(
+        `${ISSUER}/admin/approve-client/${encodeURIComponent(reg.client.clientId)}`,
+      );
+      expect(body.cli_alternative).toBe(`parachute auth approve-client ${reg.client.clientId}`);
     } finally {
       cleanup();
     }
@@ -2132,6 +2386,13 @@ describe("DCR approval gate (#74)", () => {
       expect(res.status).toBe(401);
       const body = (await res.json()) as Record<string, unknown>;
       expect(body.error).toBe("invalid_client");
+      // Same pending-affordance shape on the refresh path: a long-lived
+      // OAuth client whose row was unapproved between issuance and refresh
+      // hits this branch and surfaces the same approve_url + cli_alternative.
+      expect(body.approve_url).toBe(
+        `${ISSUER}/admin/approve-client/${encodeURIComponent(reg.client.clientId)}`,
+      );
+      expect(body.cli_alternative).toBe(`parachute auth approve-client ${reg.client.clientId}`);
     } finally {
       cleanup();
     }
@@ -2309,7 +2570,7 @@ describe("DCR auto-approve via session cookie (#199)", () => {
     // Sandbox iframes (`<iframe sandbox>` without `allow-same-origin`),
     // `data:`/`file:` documents, and some privacy contexts send the literal
     // string `Origin: null` rather than omitting the header. `new URL("null")`
-    // throws → originMatchesIssuer's try/catch returns false → DCR stays
+    // throws → isSameOriginRequest's try/catch returns false → DCR stays
     // pending. This test pins that invariant: an opaque-origin caller does
     // NOT ride the cookie path even with a valid session, because we can't
     // prove the request came from the issuer's own origin.
@@ -3556,7 +3817,7 @@ describe("inline approve button on pending /oauth/authorize (#208)", () => {
     // Opaque-origin contexts (sandboxed iframes, some `data:` and `file:`
     // pages) send the literal string "null" as the Origin header. The DCR
     // /register path covers this; the inline-approve endpoint must reject it
-    // too. originMatchesIssuer() handles this correctly because new URL("null")
+    // too. isSameOriginRequest() handles this correctly because new URL("null")
     // throws → returns false; this test pins that contract.
     const { db, cleanup } = await makeDb();
     try {