nuts-foundation / nuts-foundation/nuts-node
VDR: For a SubjectID it should be possible to create a new DID after deactivation
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
If we want users to provide a subjectID so they can map it to their internal customer administration, a deactivation of a subject should not be permanent.
Currently it is not possible to recreate a DID for a subject with a disabled DID:
level=warning msg="CreateSubject failed" error="could not store DID documents: subject already exists" module=VDR operation=CreateSubject operationID=CreateSubject requestURI=/internal/vdr/v2/subject user="<nil>"
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 tracing the VDR CreateSubject operation and the storage path producing the “subject already exists” error, then inspect how deactivated DIDs are represented. Done means a subjectID can be used to create a new DID after its previous DID is deactivated, with a regression test covering that sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100