nuts-foundation / nuts-foundation/nuts-node
Server-side caching of DID documents
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
A DID resolve always queries the database, since they're not cached server-side. Although it's a relatively cheap operation, it's an unauthenticated API call (which literally anyone can do), so there's a small DoS risk in there. This can be mitigated by caching the DID document server-side, either by building it into the Nuts node (meh) or having a reverse proxy cache the DID documents.
Note that the Nuts node's did:web resolver already cached DID documents.
Update: this also applies to the Discovery Service.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the DID resolution path and the Discovery Service endpoints, then compare their behavior with the existing did:web resolver cache. Determine how server-side caching should cover DID documents without requiring authentication. Done means repeated unauthenticated resolutions avoid querying the database while still returning the correct document.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100