Align NSS with LWS 1.0 Authentication Suite
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, nodejs
- Domain
- authentication, backend
Research direction
Start with the profile emission and authentication verifier entry points in NSS, then read the linked LWS 1.0 Authentication Suite and Controlled Identifiers specifications. Compare the proposed dual-write shape with JSS issues #319 and #320. Done means existing WebID predicates remain available while the requested CID services and selected LWS-aware verifiers are supported.
Written by the indexing model from the issue text.
Description
Context
The W3C Linked Web Storage WG published four First Public Working Drafts of the LWS 1.0 Authentication Suite on 2026-04-23:
- LWS 1.0 Authentication Suite: OpenID Connect
- LWS 1.0 Authentication Suite: SAML 2.0
- LWS 1.0 Authentication Suite: Self-signed Identity using Controlled Identifiers
- LWS 1.0 Authentication Suite: Self-signed Identity using did:key
Trust resolution across these specs relies on Controlled Identifiers v1.0 — verifiers dereference the subject URI and inspect a service[] / verificationMethod[] document.
Goal
Align NSS's WebID profile emission and auth verifiers with the LWS 1.0 suite. The intent is additive / dual-write so existing Solid clients keep working against NSS pods — the CID fields layer on top of the existing WebID predicates rather than replacing them.
Checklist
- Profile emission — CID
service[](mirrorsolid:oidcIssuer,pim:storage,ldp:inboxas typed services). Cheapest first step. - LWS10 OpenID Connect verifier
- did:key authentication
- CID self-signed authentication
- SAML 2.0 — deferred unless a concrete deployment asks
Cross-repo coordination
JavaScript Solid Server is tracking the same work:
- JSS #319 — umbrella
- JSS #320 — CID
service[]profile dual-write (same phrasing worth reusing here) - JSS #86 — did:key implementation notes
Consistency in vocabulary and profile shape across NSS + JSS (+ CSS eventually) would let the same LWS-aware clients read pods on any server.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodeSolidServer/node-solid-server
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
nodeSolidServer/node-solid-server#1848 · 2 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nodeSolidServer/node-solid-server#1841 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nodeSolidServer/node-solid-server#1147 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodeSolidServer/node-solid-server#1867 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
nodeSolidServer/node-solid-server#1852 · 1 comment ·
All issues in nodeSolidServer/node-solid-server
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
light
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
aemdemos/patients-stryker#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·