Bug

When a user registers through the browser IdP flow (POST /idp/interaction/:uid with registration), createPodStructure is called without the provisionKeys option:

// interactions.js:535
await createPodStructure(username, webId, podUri, issuer);

This means pods created via browser registration never get owner keys provisioned, even when --provision-keys / "provisionKeys": true is set in the server config.

The handleCreatePod endpoint (POST /.pods) and single-user seed path both correctly pass { provisionKeys: provisionKeysEnabled }, but the IdP registration path was missed.

Root cause

provisionKeysEnabled is not attached to the Fastify request object in the onRequest hook (server.js), so interactions.js has no way to access the config value.

Fix

1. Add request.provisionKeys = provisionKeysEnabled to the request decoration block in server.js
2. Pass { provisionKeys: request.provisionKeys } as the options argument in interactions.js:535

Related

• feat: --provision-keys flag for pod creation (Schnorr/Nostr/CID v1.0 identity) #437 (Phase 1: --provision-keys)
• feat: --provision-keys Phase 2 — wire the owner key into the WebID profile, close the LWS-CID loop (#437) #443 (Phase 2: wire key into profile)
• PR feat: --provision-keys for owner key on pod creation (#437 Phase 1) #442, PR feat: Phase 2 — wire owner key into WebID profile + did:nostr controller (#443) #444 (both merged but missed this call site)