nuts-foundation / nuts-foundation/nuts-node
Support OIDC for internal auth
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Managing internal auth with authorized_keys is a needless complication, that if anything, leads to security compromises due to administrative overhead. Since JWT bearer auth is now supported, there is no reason to use such a legacy way to configure authentication.
Instead, internal auth should be configurable by simply providing a reference OICD discovery document. Implementing it this way and just trusting organisational IDP automatically supports basic security features such as MFA, key rotation, indentity protection and conditional access.
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 reviewing the existing JWT bearer authentication support and how internal authentication currently uses authorized_keys. Done means internal authentication can be configured with an OIDC discovery document and relies on the referenced organizational identity provider instead of authorized_keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100