nuts-foundation / nuts-foundation/nuts-node
Support RSA keys in DID documents
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Currently, we only support creating DID documents with EC keys. The problem with EC keys is that some key backends (Azure Key Vault) don't support EC encryption schemes (ECDH). Decryption is used by the following Nuts node features:
- Receiving private credentials over gRPC network (although we might migrate to server-to-server issuance before this becomes a problem)
- Encrypting data (encrypt_jwt), used by KIK-v to encrypt DIDComm messages
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
The issue does not name files or tests. Start by locating DID document creation and key-handling entry points, then inspect how Azure Key Vault is used for encryption and decryption. Done means RSA keys can be represented in created DID documents and support the affected credential and DIDComm encryption paths without breaking EC keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100