Title: Profile-to-key linking aligned with LWS 1.0 (FPWDs 2026-04-23) via W3C Controlled Identifiers v1.0 · Issue #386 · JavaScriptSolidServer/JavaScriptSolidServer · GitHub
Open Graph Title: Profile-to-key linking aligned with LWS 1.0 (FPWDs 2026-04-23) via W3C Controlled Identifiers v1.0 · Issue #386 · JavaScriptSolidServer/JavaScriptSolidServer
X Title: Profile-to-key linking aligned with LWS 1.0 (FPWDs 2026-04-23) via W3C Controlled Identifiers v1.0 · Issue #386 · JavaScriptSolidServer/JavaScriptSolidServer
Description: Tracker for converging the existing profile/key-linking issues (#42, #6, #4, #39, #86, #319) onto the W3C Linked Web Storage 1.0 Authentication Suite FPWDs published 2026-04-23 — and on the substrate they delegate to, W3C Controlled Iden...
Open Graph Description: Tracker for converging the existing profile/key-linking issues (#42, #6, #4, #39, #86, #319) onto the W3C Linked Web Storage 1.0 Authentication Suite FPWDs published 2026-04-23 — and on the substra...
X Description: Tracker for converging the existing profile/key-linking issues (#42, #6, #4, #39, #86, #319) onto the W3C Linked Web Storage 1.0 Authentication Suite FPWDs published 2026-04-23 — and on the substra...
Opengraph URL: https://github.com/JavaScriptSolidServer/JavaScriptSolidServer/issues/386
X: @github
Domain: github.com
IPv4 address: 140.82.114.3
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Profile-to-key linking aligned with LWS 1.0 (FPWDs 2026-04-23) via W3C Controlled Identifiers v1.0","articleBody":"**Tracker** for converging the existing profile/key-linking issues (#42, #6, #4, #39, #86, #319) onto the **W3C Linked Web Storage 1.0 Authentication Suite** FPWDs published 2026-04-23 — and on the substrate they delegate to, **W3C Controlled Identifiers v1.0**.\n\nThis issue does not propose a new design from scratch. It captures the design that fell out of reading the LWS FPWDs against JSS's current state, so future PRs can reference one place.\n\n---\n\n## Key insight\n\n**LWS auth FPWDs delegate identity-document semantics to [W3C Controlled Identifiers 1.0](https://www.w3.org/TR/cid-1.0/).** A WebID becomes LWS-conformant for self-signed auth (LWS10-CID, LWS10-did:key) by *being* a valid CID document — i.e. by carrying `verificationMethod`, `authentication`, `assertionMethod`, `controller`, `publicKeyJwk`/`publicKeyMultibase` triples. No separate DID document needed for the WebID-controlled case.\n\nThis converges several historically separate JSS workstreams onto one mechanism.\n\n---\n\n## Current JSS state\n\n`src/webid/profile.js` already declares `cid:` and `lws:` prefixes (prep work landed) but writes zero verification material. The path to conformance is **additive** — no breaking changes to existing profiles.\n\n---\n\n## Proposed profile shape\n\nA WebID with three keys: a Nostr secp256k1 (NIP-98), a did:key Ed25519 (LWS10), and a passkey/WebAuthn credential.\n\n```jsonld\n{\n \"@context\": [\n \"https://www.w3.org/ns/cid/v1\",\n {\n \"foaf\": \"http://xmlns.com/foaf/0.1/\",\n \"solid\": \"http://www.w3.org/ns/solid/terms#\",\n \"schema\": \"http://schema.org/\",\n \"pim\": \"http://www.w3.org/ns/pim/space#\",\n \"ldp\": \"http://www.w3.org/ns/ldp#\",\n \"owl\": \"http://www.w3.org/2002/07/owl#\",\n \"lws\": \"https://www.w3.org/ns/lws#\",\n \"nostr\": \"https://w3id.org/nostr/vocab#\",\n \"alsoKnownAs\": { \"@id\": \"https://www.w3.org/ns/activitystreams#alsoKnownAs\", \"@type\": \"@id\" },\n \"sameAs\": { \"@id\": \"owl:sameAs\", \"@type\": \"@id\" }\n }\n ],\n \"id\": \"https://alice.solid.social/profile/card.jsonld#me\",\n \"type\": [\"foaf:Person\"],\n \"controller\": \"https://alice.solid.social/profile/card.jsonld#me\",\n\n \"verificationMethod\": [\n { \"id\": \"...#nostr-key-1\", \"type\": \"Multikey\", \"controller\": \"...#me\", \"publicKeyMultibase\": \"fe70102…\" },\n { \"id\": \"...#did-key-1\", \"type\": \"Multikey\", \"controller\": \"...#me\", \"publicKeyMultibase\": \"z6MkpT…\" },\n { \"id\": \"...#passkey-1\", \"type\": \"JsonWebKey\", \"controller\": \"...#me\", \"publicKeyJwk\": { \"kty\": \"EC\", \"crv\": \"P-256\", \"x\": \"…\", \"y\": \"…\" } }\n ],\n \"authentication\": [\"...#nostr-key-1\", \"...#did-key-1\", \"...#passkey-1\"],\n \"assertionMethod\": [\"...#did-key-1\"],\n\n \"alsoKnownAs\": [\"did:nostr:124c0…\", \"did:key:z6Mk…\"],\n \"sameAs\": \"did:nostr:124c0…\"\n}\n```\n\nNotes:\n- `https://www.w3.org/ns/cid/v1` is the **first** `@context` entry. CID-aware verifiers process this directly; existing JSS predicates (`oidcIssuer`, `pim:storage`, `ldp:inbox`, `service`, …) live in the inline prefix object so JSON-LD output is byte-stable for everything else.\n- Nostr secp256k1 uses did:nostr's multikey recipe (parity byte + multicodec `0xe7,0x01` + base16-lower) so a NIP-98 verifier can decode straight to the 32-byte x-only key without dereferencing a DID document.\n- `alsoKnownAs` is the forward link to DID URIs (matches did:nostr's conventional binding); `sameAs` keeps the existing `src/auth/did-nostr.js` resolver working unchanged.\n\n---\n\n## Verification flow (key K → WebID W)\n\n1. Identify subject from credential: `sub` (LWS-CID JWT), pubkey hex (NIP-98), DID URI (did:key), credential ID (WebAuthn)\n2. Fetch the WebID profile (which **is** the CID document)\n3. Find matching `verificationMethod` — by `kid` for JWT, by raw key match for NIP-98\n4. Confirm it appears in `authentication` (or `assertionMethod` for credential issuance)\n5. Verify the cryptographic proof using that key\n6. Confirm the verification method's `controller` is W (or W is its own controller)\n\nThis is **profile-only** for LWS-CID and WebAuthn; **profile-or-DID-doc** for did:nostr (existing two-way `owl:sameAs` ↔ `alsoKnownAs` from #42); **DID-doc-only** for did:key (the DID *is* the public key).\n\n---\n\n## Migration path\n\nSmallest delta — ~80–120 LOC:\n\n| Change | Where |\n|---|---|\n| Switch `@context` to array form so `cid/v1` is the imported context | `src/webid/profile.js:generateProfileJsonLd` |\n| Accept `keys[]` parameter; emit `verificationMethod` + `authentication` (+ optional `assertionMethod`) when supplied | same |\n| Pass keys through from signup (nostr pubkey, did:key, passkey credential) | `src/handlers/container.js:createPodStructure`, `src/idp/interactions.js` registration paths |\n| `jss migrate add-keys` admin command to upgrade existing pods (idempotent merge — only adds triples) | new `bin/jss.js` subcommand |\n\nBack-compat: profiles created without keys are byte-identical to today. Existing JSS resolvers (did-nostr, webid-tls) continue to work; the new design generalises the WebID-TLS pattern (`cert:key` → `verificationMethod`).\n\n---\n\n## Open spec choices (FPWDs don't bind us; we get to decide)\n\n| # | Question | Suggested default |\n|---|---|---|\n| 1 | Profile vs DID-doc primary | WebID is canonical for LWS-CID; DID docs supplementary via `alsoKnownAs` |\n| 2 | `kid` fragment shape | `#\u003cpurpose>-\u003cn>`, never reuse after revocation |\n| 3 | Key rotation | Append-only `verificationMethod`; revoked keys removed from `authentication` but stay with `expirationDate` |\n| 4 | NIP-98 Schnorr inside CID's Multikey | Use did:nostr's encoding verbatim; no `NostrPublicKey` extension |\n| 5 | Passkey/WebAuthn vocabulary | `JsonWebKey` (P-256 EC); `credentialId` stays in private account record, not profile |\n| 6 | `alsoKnownAs` provenance | Bidirectional check for did:nostr (existing); trust WebID-side for did:key (no DID doc) |\n| 7 | `controller` self-reference vs delegation | Self-control only for v1; delegation/recovery later |\n| 8 | Recovery keys | `lws:recoveryMethod` extension until standardised |\n| 9 | `assertionMethod` membership | Only did:key for now (Schnorr/passkey are auth-only in practice) |\n| 10 | Profile MIME content negotiation | Existing `application/ld+json` at `profile/card.jsonld` already conforms |\n\n---\n\n## Phasing\n\nThis tracker captures design. Concrete shippable phases:\n\n**Phase 1 — Profile emits keys** (PR-shaped):\n- `src/webid/profile.js` accepts `keys[]`; emits CID triples\n- `@context` array form\n- New pods at signup get the keys they registered with\n- No verifier-side changes yet — purely additive\n- Tests for the JSON-LD structure\n\n**Phase 2 — Migration command**:\n- `jss migrate add-keys` to upgrade existing pods\n- Idempotent; safe to re-run\n\n**Phase 3 — LWS10-CID verifier**:\n- Server-side support for LWS-CID JWTs (`sub`/`iss`/`client_id` triple equality, `kid` lookup)\n- Existing did:nostr / WebID-TLS verifiers stay; new LWS-CID joins them\n- This is what #319 / #86 actually need\n\n**Phase 4 — Cross-protocol unification**:\n- Single \"self-signed identity\" verifier wrapping NIP-98, LWS-CID, did:key, WebID-TLS\n- All four resolve K→W against the same `verificationMethod`/`authentication` declarations\n- Auth-method preference order (#306) becomes a config\n\n---\n\n## Refs\n\n- [W3C Controlled Identifiers v1.0](https://www.w3.org/TR/cid-1.0/)\n- [LWS 1.0 Authentication: SSI via Controlled Identifiers (FPWD 2026-04-23)](https://www.w3.org/TR/2026/WD-lws10-authn-ssi-cid-20260423/)\n- [LWS 1.0 Authentication: SSI via did:key (FPWD 2026-04-23)](https://www.w3.org/TR/2026/WD-lws10-authn-ssi-did-key-20260423/)\n- [W3C news announcement](https://www.w3.org/news/2026/first-public-working-drafts-for-the-linked-web-storage-lws-1-0-authentication-suite/)\n- [did:nostr DID Method Specification](https://nostrcg.github.io/did-nostr/)\n\n## Converges these issues\n\n- #42 (Spec: did:nostr → WebID Resolution)\n- #319 (Align JSS auth modules with LWS 1.0 FPWDs)\n- #6 (Phase 2: Link did:nostr to WebID profiles via owl:sameAs)\n- #4 (did:nostr SSO + Schnorr/NIP-98 — done; this is the LWS-aligned next step)\n- #39 (Tests for did:nostr → WebID resolution)\n- #86 (Support did:key Authentication, LWS10 Spec)\n- #87 (LWS Protocol Mode Support — separate concern: data plane, not auth)\n- #89 (Extract Minimal Viable LWS Server)\n- #67 (WebID-TLS — the existing precedent for \"profile declares its keys\")\n- #306 (Auth middleware preference order)","author":{"url":"https://github.com/melvincarvalho","@type":"Person","name":"melvincarvalho"},"datePublished":"2026-05-09T03:57:46Z","url":"https://github.com/JavaScriptSolidServer/JavaScriptSolidServer/issues/386"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:f9dcf61c-611a-d043-8549-954efcdf22f1 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 833E:C707B:E125B1:11DF9C8:6B037D44 |
| html-safe-nonce | 2a12a98da81afd9b0e7e20cb89dc71a6f6883cbbbc2a33078cc0bc7f5ce1a25f |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4MzNFOkM3MDdCOkUxMjVCMToxMURGOUM4OjZCMDM3RDQ0IiwidmlzaXRvcl9pZCI6IjY4NzE1NDU1NDYxOTc0MDA5MDAiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 4b7a06facbf2d641514ce945a1763735f2c140d1778d353a04a05f2a5a2e241c |
| hovercard-subject-tag | issue:4411004463 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/JavaScriptSolidServer/JavaScriptSolidServer/386/issue_layout |
| twitter:image | https://opengraph.githubassets.com/313aa8a506870e18dbf7d7b1af166afd7aa5e03eb3d3bc7336e9ba7e473afb56/JavaScriptSolidServer/JavaScriptSolidServer/issues/386 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/313aa8a506870e18dbf7d7b1af166afd7aa5e03eb3d3bc7336e9ba7e473afb56/JavaScriptSolidServer/JavaScriptSolidServer/issues/386 |
| og:image:alt | Tracker for converging the existing profile/key-linking issues (#42, #6, #4, #39, #86, #319) onto the W3C Linked Web Storage 1.0 Authentication Suite FPWDs published 2026-04-23 — and on the substra... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | melvincarvalho |
| hostname | github.com |
| expected-hostname | github.com |
| None | 87e774ee7c6b3bee0490394e4d3e57ec9dbc956f74b87ea685dc8996c1676456 |
| turbo-cache-control | no-preview |
| go-import | github.com/JavaScriptSolidServer/JavaScriptSolidServer git https://github.com/JavaScriptSolidServer/JavaScriptSolidServer.git |
| octolytics-dimension-user_id | 205442424 |
| octolytics-dimension-user_login | JavaScriptSolidServer |
| octolytics-dimension-repository_id | 958025407 |
| octolytics-dimension-repository_nwo | JavaScriptSolidServer/JavaScriptSolidServer |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 958025407 |
| octolytics-dimension-repository_network_root_nwo | JavaScriptSolidServer/JavaScriptSolidServer |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 423dbb54c5e7bfecc838eb387c1435eb3d0e760d |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
| Server | github.com |
| Content-Type | text/html; charset=utf-8 |
| Cache-Control | max-age=0, private, must-revalidate |
Viewport: width=device-width