@deque/axe-auth 1.1.0-next.82d244e3 → 1.1.0-next.8e6dbb34

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,25 +1,50 @@
1
1
  "use strict";
2
2
  Object.defineProperty(exports, "__esModule", { value: true });
3
3
  exports.KeyringTokenStore = exports.STORED_BLOB_VERSION = void 0;
4
+ exports.shouldChunkForKeyring = shouldChunkForKeyring;
4
5
  exports.parseAndMigrateBlob = parseAndMigrateBlob;
6
+ exports.keyringErrorMessage = keyringErrorMessage;
5
7
  exports.platformKeyringHint = platformKeyringHint;
8
+ exports.chunkBlobForKeyring = chunkBlobForKeyring;
6
9
  const errors_1 = require("./errors");
7
10
  const keyringBinding_1 = require("./keyringBinding");
8
- // On macOS: Keychain generic password item with the service name below.
9
- // On Windows: Credential Manager entry. On Linux: Secret Service / libsecret.
10
- // Exposed as a human-readable string because these all surface the service
11
- // name in OS UIs (Keychain Access, credmgr.exe, seahorse).
12
11
  const SERVICE_NAME = "axe-auth";
13
- // Single keychain entry per machine. The blob it holds is fully
14
- // self-describing (issuerURL, clientId, allowInsecureIssuer, plus the
15
- // tokens), so verbs that don't pass `--server` / `--realm` /
16
- // `--client-id` can resolve their config from the entry.
17
- //
18
- // Account name is human-readable so users investigating the entry in
19
- // macOS Keychain Access (or `secret-tool` on Linux, credmgr on
20
- // Windows) can tell what it is. Not versioned: the schema version
21
- // lives inside the blob and migrators handle the upgrade path.
12
+ /**
13
+ * Keychain account identifier. On macOS/Linux the entire blob lives at
14
+ * this single account. On Windows the blob is base64-encoded and split
15
+ * across `credentials.0`, `credentials.1`, entries (see `CHUNK_LIMIT`),
16
+ * so a Windows dev inspecting Credential Manager will see opaque base64.
17
+ */
22
18
  const ACCOUNT_NAME = "credentials";
19
+ /**
20
+ * Max JS string length per chunk. The limit applies to the full chunk
21
+ * including chunk 0's `<N>\n` count header, so chunk 0's data slice is
22
+ * `CHUNK_LIMIT - headerLen`. Windows Credential Manager's per-entry
23
+ * cap is `CRED_MAX_CREDENTIAL_BLOB_SIZE = 2560` bytes, and the
24
+ * `@napi-rs/keyring` Windows backend stores strings as UTF-16 (2 bytes
25
+ * per char), so 1250 chars = 2500 bytes stays safely under the cap.
26
+ */
27
+ const CHUNK_LIMIT = 1250;
28
+ /**
29
+ * Cap on chunks per stored blob. A request that would exceed this
30
+ * raises `TOKEN_TOO_LARGE` so an IDP issuing tokens with extraordinary
31
+ * claim counts fails with a clear error instead of silently consuming
32
+ * dozens of keychain entries.
33
+ */
34
+ const MAX_CHUNKS = 32;
35
+ /**
36
+ * Whether `KeyringTokenStore` should split the stored blob across
37
+ * multiple keychain entries on this platform. Windows-only: Credential
38
+ * Manager has a 2560-byte per-entry cap that large OAuth tokens
39
+ * routinely exceed. macOS Keychain and Linux libsecret have no
40
+ * comparable limit, and on macOS each entry is independently lockable
41
+ * (chunking there would multiply per-entry ACL prompts). Exported
42
+ * (parameterized for tests) so the chunking path can be exercised
43
+ * deterministically.
44
+ */
45
+ function shouldChunkForKeyring(platform = process.platform) {
46
+ return platform === "win32";
47
+ }
23
48
  /**
24
49
  * Current on-disk blob schema version. Exported so consumers can
25
50
  * display "stored v:N, expected v:M" diagnostics when `load()` returns
@@ -127,10 +152,6 @@ function parseAndMigrateBlob(raw, expectedVersion = exports.STORED_BLOB_VERSION,
127
152
  const storedVersion = getStoredVersion(parsed);
128
153
  if (storedVersion === null)
129
154
  return { ok: false, reason: "corrupt" };
130
- // Walk the migrator chain until we reach the expected version. A
131
- // missing or null-returning migrator means the old blob cannot be
132
- // upgraded; surface that so callers can prompt re-auth with a
133
- // clear signal instead of silently returning `empty`.
134
155
  let current = parsed;
135
156
  let currentVersion = storedVersion;
136
157
  while (currentVersion !== expectedVersion) {
@@ -144,8 +165,6 @@ function parseAndMigrateBlob(raw, expectedVersion = exports.STORED_BLOB_VERSION,
144
165
  }
145
166
  const nextVersion = getStoredVersion(next);
146
167
  if (nextVersion === null || nextVersion <= currentVersion) {
147
- // Migrator output is malformed or didn't advance. Treat the
148
- // stored blob as un-migratable rather than loop forever.
149
168
  return { ok: false, reason: "version-mismatch", storedVersion };
150
169
  }
151
170
  current = next;
@@ -154,8 +173,29 @@ function parseAndMigrateBlob(raw, expectedVersion = exports.STORED_BLOB_VERSION,
154
173
  return { ok: true, blob: current };
155
174
  }
156
175
  function wrapKeyringError(op, cause) {
176
+ // Pass-through pre-wrapped OAuthFlowErrors so we don't double-wrap
177
+ // our own error type. The most common source today is
178
+ // `defaultEntryFactory` throwing `KEYRING_UNAVAILABLE` when the
179
+ // native binding can't be loaded — relabelling that as another
180
+ // `KEYRING_UNAVAILABLE` with a duplicate message and a possibly
181
+ // misleading platform hint helps nobody.
182
+ if (cause instanceof errors_1.OAuthFlowError) {
183
+ throw cause;
184
+ }
185
+ throw new errors_1.OAuthFlowError("KEYRING_UNAVAILABLE", keyringErrorMessage(op, cause), {
186
+ cause,
187
+ });
188
+ }
189
+ /**
190
+ * Builds the user-facing keychain error message: the underlying
191
+ * cause's text plus a per-platform hint. Platform is a parameter
192
+ * (defaulting to `process.platform`) so tests can drive each branch
193
+ * without mocking the runtime; mirrors the pattern in
194
+ * `platformKeyringHint`.
195
+ */
196
+ function keyringErrorMessage(op, cause, platform = process.platform) {
157
197
  const causeMessage = cause instanceof Error ? cause.message : String(cause);
158
- throw new errors_1.OAuthFlowError("KEYRING_UNAVAILABLE", `System keychain ${op} failed: ${causeMessage}. ${platformKeyringHint()}`, { cause });
198
+ return `System keychain ${op} failed: ${causeMessage}. ${platformKeyringHint(platform)}`;
159
199
  }
160
200
  /**
161
201
  * Returns a per-platform hint appended to keychain error messages so
@@ -176,30 +216,119 @@ function platformKeyringHint(platform = process.platform) {
176
216
  return `Underlying platform: ${platform}.`;
177
217
  }
178
218
  }
219
+ /**
220
+ * Parses chunk 0's `<N>\n<rest>` header. Returns the chunk count and
221
+ * the data part following the newline, or `null` for any malformed /
222
+ * out-of-range / non-canonically-encoded header. Centralised here
223
+ * (rather than open-coded twice in `#loadChunked` and
224
+ * `#previousChunkN`) so the canonical-encoding contract has one
225
+ * authoritative implementation.
226
+ */
227
+ function parseChunkHeader(first) {
228
+ const newlineIdx = first.indexOf("\n");
229
+ if (newlineIdx <= 0)
230
+ return null;
231
+ const nStr = first.slice(0, newlineIdx);
232
+ const n = parseInt(nStr, 10);
233
+ // Reject non-canonical encodings ("01", " 3", "3abc"). parseInt is
234
+ // permissive about those; we want a single canonical encoding so
235
+ // two different headers can't decode to the same N.
236
+ if (!Number.isInteger(n) || n < 1 || n > MAX_CHUNKS || String(n) !== nStr) {
237
+ return null;
238
+ }
239
+ return { n, rest: first.slice(newlineIdx + 1) };
240
+ }
179
241
  /**
180
242
  * `TokenStore` backed by the operating system's native keychain via
181
243
  * `@napi-rs/keyring` (macOS Keychain, Windows Credential Manager, Linux
182
- * Secret Service). One entry per machine, keyed by a fixed account
183
- * name; the blob carries its own issuer/client coordinates so verbs
184
- * can recover full config without per-issuer keying.
244
+ * Secret Service). On macOS and Linux the blob lives in a single entry
245
+ * keyed by the fixed `credentials` account name. On Windows the blob
246
+ * is split across `credentials.0`, `credentials.1`, entries to fit
247
+ * under Credential Manager's 2560-byte (1280 UTF-16 char) per-entry
248
+ * cap; see `shouldChunkForKeyring`.
249
+ *
250
+ * The blob carries its own issuer/client coordinates so verbs can
251
+ * recover full config without per-issuer keying.
185
252
  */
186
253
  class KeyringTokenStore {
187
- #entry;
254
+ #entryFactory;
255
+ #chunked;
256
+ /**
257
+ * @param entryFactory Injection seam for `@napi-rs/keyring` entries.
258
+ * Defaults to the production lazy-resolved factory; tests pass a
259
+ * recording / faking variant.
260
+ */
188
261
  constructor(entryFactory = keyringBinding_1.defaultEntryFactory) {
189
- this.#entry = entryFactory(SERVICE_NAME, ACCOUNT_NAME);
262
+ this.#entryFactory = entryFactory;
263
+ this.#chunked = shouldChunkForKeyring();
264
+ }
265
+ /**
266
+ * @internal Test seam. Constructs a store with an explicit chunking
267
+ * decision instead of the platform-determined default, so the
268
+ * chunked path can be exercised on macOS/Linux CI and the unchunked
269
+ * path on Windows CI. Production code must use the regular
270
+ * constructor and let `shouldChunkForKeyring()` decide — passing
271
+ * `chunked: true` on macOS would write data that the regular
272
+ * constructor wouldn't be able to read.
273
+ */
274
+ static forTesting(entryFactory, chunked) {
275
+ const store = new KeyringTokenStore(entryFactory);
276
+ store.#chunked = chunked;
277
+ return store;
278
+ }
279
+ #entry(account) {
280
+ return this.#entryFactory(SERVICE_NAME, account);
190
281
  }
191
282
  async save(entry) {
192
- try {
193
- this.#entry.setPassword(JSON.stringify(entryToBlob(entry)));
283
+ const jsonBlob = JSON.stringify(entryToBlob(entry));
284
+ if (this.#chunked) {
285
+ // Encode + chunk OUTSIDE the try/catch so a TOKEN_TOO_LARGE from
286
+ // `chunkBlobForKeyring` surfaces unchanged. The keychain
287
+ // operations stay inside the try and get wrapped as
288
+ // KEYRING_UNAVAILABLE if they fail.
289
+ const encoded = Buffer.from(jsonBlob, "utf8").toString("base64");
290
+ const parts = chunkBlobForKeyring(encoded);
291
+ try {
292
+ this.#saveChunked(parts);
293
+ }
294
+ catch (cause) {
295
+ wrapKeyringError("write", cause);
296
+ }
194
297
  }
195
- catch (cause) {
196
- wrapKeyringError("write", cause);
298
+ else {
299
+ try {
300
+ this.#entry(ACCOUNT_NAME).setPassword(jsonBlob);
301
+ }
302
+ catch (cause) {
303
+ wrapKeyringError("write", cause);
304
+ }
197
305
  }
198
306
  }
199
307
  async load() {
200
308
  let raw;
201
309
  try {
202
- raw = this.#entry.getPassword();
310
+ if (this.#chunked) {
311
+ const result = this.#loadChunked();
312
+ if (result.kind === "present") {
313
+ raw = result.blob;
314
+ }
315
+ else if (result.kind === "empty") {
316
+ // First-time-upgrade fallback: a Windows dev who upgraded
317
+ // across the chunking change has data at the bare
318
+ // `credentials` account but no chunks yet. Read that legacy
319
+ // entry; the next save() migrates it. Note we only fall
320
+ // back when chunked data is *empty* — when chunked data is
321
+ // *corrupt* we surface that directly rather than restoring
322
+ // potentially stale legacy data underneath the corruption.
323
+ raw = this.#entry(ACCOUNT_NAME).getPassword();
324
+ }
325
+ else {
326
+ return { ok: false, reason: "corrupt" };
327
+ }
328
+ }
329
+ else {
330
+ raw = this.#entry(ACCOUNT_NAME).getPassword();
331
+ }
203
332
  }
204
333
  catch (cause) {
205
334
  wrapKeyringError("read", cause);
@@ -213,11 +342,204 @@ class KeyringTokenStore {
213
342
  }
214
343
  async clear() {
215
344
  try {
216
- this.#entry.deletePassword();
345
+ if (this.#chunked) {
346
+ this.#clearChunked();
347
+ }
348
+ else {
349
+ this.#entry(ACCOUNT_NAME).deletePassword();
350
+ }
217
351
  }
218
352
  catch (cause) {
219
353
  wrapKeyringError("delete", cause);
220
354
  }
221
355
  }
356
+ /**
357
+ * Writes `parts` (the output of `chunkBlobForKeyring`) to entries
358
+ * `credentials.0..N-1`.
359
+ *
360
+ * Writes are in **reverse index order** — chunks N-1..1, then chunk
361
+ * 0 with the new header last. Chunk 0's header is what reads use to
362
+ * learn N, so until it's overwritten the previous chunk 0 still
363
+ * references the previous N chunks.
364
+ *
365
+ * Crash recovery is partial, not total. Reverse order helps in one
366
+ * case: when N_new > N_old and the crash happens before chunk 0 is
367
+ * rewritten — writes to indices >= N_old don't disturb old data,
368
+ * the previous chunk 0 still references the previous N chunks, and
369
+ * the prior session survives. The typical refresh case (N_new ==
370
+ * N_old) overwrites chunks 1..N-1 with new data while chunk 0 is
371
+ * still old, so a crash there reads as corrupt and the user
372
+ * re-auths. Reverse order is therefore a marginal improvement over
373
+ * forward order, not a guarantee.
374
+ *
375
+ * Cleanup sweeps `[N_new, N_old)` (bounded by the previous chunk
376
+ * count read from the old chunk 0 header before we overwrite it).
377
+ * For a typical token refresh (same N) this is zero deletes; the
378
+ * full safety sweep up to MAX_CHUNKS only runs as a defensive
379
+ * recovery when the previous N can't be determined. Orphans at
380
+ * indices >= max(N_new, N_old) from interrupted resize-up writes
381
+ * persist until the next `clear()` does the full sweep.
382
+ *
383
+ * Concurrency: this method is not safe to run concurrently against
384
+ * the same OS keychain. Two writers can interleave at chunk
385
+ * boundaries and produce a Frankenstein blob. axe-auth runs as a
386
+ * short-lived CLI so this is unlikely in practice, but a long-lived
387
+ * process refreshing in the background while the CLI is invoked
388
+ * could trip it.
389
+ */
390
+ #saveChunked(parts) {
391
+ const previousN = this.#previousChunkN();
392
+ for (let i = parts.length - 1; i >= 1; i--) {
393
+ this.#entry(`${ACCOUNT_NAME}.${i}`).setPassword(parts[i]);
394
+ }
395
+ this.#entry(`${ACCOUNT_NAME}.0`).setPassword(parts[0]);
396
+ // Best-effort sweep: writes have already succeeded, so a sweep
397
+ // failure shouldn't roll back the save. The next save's bounded
398
+ // sweep cleans up anything we miss here. Same reasoning for the
399
+ // legacy delete below.
400
+ const sweepEnd = previousN ?? MAX_CHUNKS;
401
+ for (let i = parts.length; i < sweepEnd; i++) {
402
+ try {
403
+ this.#entry(`${ACCOUNT_NAME}.${i}`).deletePassword();
404
+ }
405
+ catch {
406
+ // Sweep is best-effort; the next save handles leftovers.
407
+ }
408
+ }
409
+ // Clear any pre-chunking single-entry blob from a previous
410
+ // axe-auth release. This is a forever-tax (one extra
411
+ // deletePassword per save even after the migration is done)
412
+ // because we have no per-machine "migration completed" flag;
413
+ // adding one would mean another keychain entry to manage. The
414
+ // cost is one Credential Manager call per refresh — negligible
415
+ // relative to the OAuth round-trip.
416
+ try {
417
+ this.#entry(ACCOUNT_NAME).deletePassword();
418
+ }
419
+ catch {
420
+ // Best-effort; the next save attempts again.
421
+ }
422
+ }
423
+ /**
424
+ * Reads the chunk-count header from `credentials.0` so `#saveChunked`
425
+ * can bound its cleanup sweep. Returns `null` when chunk 0 is
426
+ * missing, when the header is malformed, or when the encoded N is
427
+ * out of range — every "I don't know the previous count" case
428
+ * collapses to a full safety sweep at the call site.
429
+ */
430
+ #previousChunkN() {
431
+ const first = this.#entry(`${ACCOUNT_NAME}.0`).getPassword();
432
+ if (first === null)
433
+ return null;
434
+ return parseChunkHeader(first)?.n ?? null;
435
+ }
436
+ /**
437
+ * Reverse of `#saveChunked`. Returns a discriminated result so the
438
+ * caller can distinguish "no data" from "data is malformed" without
439
+ * reaching for sentinel strings.
440
+ */
441
+ #loadChunked() {
442
+ const first = this.#entry(`${ACCOUNT_NAME}.0`).getPassword();
443
+ if (first === null)
444
+ return { kind: "empty" };
445
+ const header = parseChunkHeader(first);
446
+ if (!header)
447
+ return { kind: "corrupt" };
448
+ const parts = [header.rest];
449
+ for (let i = 1; i < header.n; i++) {
450
+ const part = this.#entry(`${ACCOUNT_NAME}.${i}`).getPassword();
451
+ if (part === null)
452
+ return { kind: "corrupt" };
453
+ parts.push(part);
454
+ }
455
+ // `Buffer.from(_, 'base64')` is permissive — invalid characters
456
+ // are silently dropped rather than throwing. Garbage base64
457
+ // produces garbage UTF-8, which falls through to the upstream
458
+ // JSON.parse and surfaces as `corrupt` from
459
+ // `parseAndMigrateBlob`. So no try/catch is needed here.
460
+ const blob = Buffer.from(parts.join(""), "base64").toString("utf8");
461
+ return { kind: "present", blob };
462
+ }
463
+ #clearChunked() {
464
+ // Sweep the whole safety range rather than break-on-first-missing
465
+ // so chunk holes (from interrupted writes or manual tampering)
466
+ // still get cleaned up. Logout is rare enough that the
467
+ // unconditional sweep cost is irrelevant.
468
+ //
469
+ // Per-entry errors are caught locally so a single throw doesn't
470
+ // strand the remaining chunks (or the legacy entry) in the
471
+ // keychain. After all attempts, we surface the first failure so
472
+ // the user still sees that logout didn't fully complete.
473
+ let firstError = null;
474
+ for (let i = 0; i < MAX_CHUNKS; i++) {
475
+ try {
476
+ this.#entry(`${ACCOUNT_NAME}.${i}`).deletePassword();
477
+ }
478
+ catch (cause) {
479
+ firstError ??= cause;
480
+ }
481
+ }
482
+ // And the pre-chunking single-entry blob, in case a Windows dev
483
+ // had axe-auth installed before chunking shipped.
484
+ try {
485
+ this.#entry(ACCOUNT_NAME).deletePassword();
486
+ }
487
+ catch (cause) {
488
+ firstError ??= cause;
489
+ }
490
+ if (firstError !== null) {
491
+ throw firstError;
492
+ }
493
+ }
222
494
  }
223
495
  exports.KeyringTokenStore = KeyringTokenStore;
496
+ /**
497
+ * Splits `blob` into the N parts that `KeyringTokenStore.#saveChunked`
498
+ * writes to `credentials.0..N-1`. Chunk 0 is prefixed with `<N>\n` so
499
+ * the reader can learn N from a single getPassword call. Each chunk
500
+ * stays under `CHUNK_LIMIT` UTF-16 characters; throws if the blob would
501
+ * require more than `MAX_CHUNKS` chunks. Exported for tests.
502
+ */
503
+ function chunkBlobForKeyring(blob) {
504
+ // N depends on the header length, which depends on N. Solve by
505
+ // iterating until the chunk count stabilises (converges in <= a
506
+ // couple of steps for any realistic blob). The safety counter is
507
+ // belt-and-suspenders against a future tweak (different
508
+ // CHUNK_LIMIT, different header format) accidentally introducing
509
+ // oscillation; an unbounded loop here would hang `axe-auth login`
510
+ // with no error.
511
+ let n = Math.max(1, Math.ceil(blob.length / CHUNK_LIMIT));
512
+ let safety = 0;
513
+ while (true) {
514
+ if (++safety > 8) {
515
+ throw new Error(`chunkBlobForKeyring: chunk count failed to converge after ${safety} iterations (blob length ${blob.length})`);
516
+ }
517
+ const headerLen = String(n).length + 1; // "<N>\n"
518
+ const chunk0Capacity = CHUNK_LIMIT - headerLen;
519
+ if (chunk0Capacity <= 0) {
520
+ throw new Error(`chunkBlobForKeyring: chunk count ${n} leaves no room for data`);
521
+ }
522
+ const remaining = Math.max(0, blob.length - chunk0Capacity);
523
+ const next = 1 + Math.ceil(remaining / CHUNK_LIMIT);
524
+ if (next === n)
525
+ break;
526
+ n = next;
527
+ }
528
+ if (n > MAX_CHUNKS) {
529
+ // Surfaced as a distinct error code (rather than KEYRING_UNAVAILABLE)
530
+ // because the keystore is healthy — the failure is that the IDP's
531
+ // token has too many claims to fit. Wrapping this as a keychain
532
+ // error would attach a misleading "Credential Manager rejected"
533
+ // platform hint via `wrapKeyringError`'s default path.
534
+ throw new errors_1.OAuthFlowError("TOKEN_TOO_LARGE", `OAuth token blob would require ${n} keyring entries (max ${MAX_CHUNKS}). The IDP may be issuing tokens with unusually many claims; talk to the realm administrator.`);
535
+ }
536
+ const headerLen = String(n).length + 1;
537
+ const chunk0Capacity = CHUNK_LIMIT - headerLen;
538
+ const parts = [`${n}\n${blob.slice(0, chunk0Capacity)}`];
539
+ let pos = chunk0Capacity;
540
+ while (pos < blob.length) {
541
+ parts.push(blob.slice(pos, pos + CHUNK_LIMIT));
542
+ pos += CHUNK_LIMIT;
543
+ }
544
+ return parts;
545
+ }
package/package.json CHANGED
@@ -1,8 +1,15 @@
1
1
  {
2
2
  "name": "@deque/axe-auth",
3
- "version": "1.1.0-next.82d244e3",
3
+ "version": "1.1.0-next.8e6dbb34",
4
4
  "description": "CLI authentication utility for Deque services",
5
5
  "license": "SEE LICENSE IN LICENSE",
6
+ "repository": {
7
+ "type": "git",
8
+ "url": "https://github.com/dequelabs/axe-mcp-server-public.git"
9
+ },
10
+ "bugs": {
11
+ "url": "https://github.com/dequelabs/axe-mcp-server-public/issues"
12
+ },
6
13
  "type": "commonjs",
7
14
  "main": "dist/index.js",
8
15
  "types": "dist/index.d.ts",
@@ -34,11 +41,12 @@
34
41
  "c8": "^10.1.3",
35
42
  "hono": "^4.12.16",
36
43
  "tsx": "^4.20.6",
37
- "typescript": "^5.9.3"
44
+ "typescript": "^6.0.3"
38
45
  },
39
46
  "scripts": {
40
47
  "build": "tsc",
41
- "test": "tsx --test 'src/**/*.test.ts'",
48
+ "typecheck:scripts": "tsc -p tsconfig.scripts.json",
49
+ "test": "tsx --test \"src/**/*.test.ts\"",
42
50
  "coverage": "c8 pnpm test",
43
51
  "register-dev-client": "tsx scripts/registerDevClient.ts",
44
52
  "smoke-authorize": "tsx scripts/smokeAuthorize.ts",