Update `api-keys` service to include `ownerNcaId` in the key validation result
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Description
API Keys Service is used only in the self-hosted/OSS environment. It's endpoint generates the exact same response that the UAM policy evaluation does in the managed environment. The response from API Keys Service should:
- use the value of top level
nca_idclaim as the value of the newownerNcaIdfield - use the value of
authorizations.ncaIdclaim as the value of the existingncaIdfield
The new field will not be used till other changes are performed.
By submitting this issue, you acknowledge that you are an assigned member of the NVCF development team and agree to follow our code of conduct and our contributing guidelines.
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.
Research direction
Start in the Go implementation of the api-keys service endpoint that validates keys and builds its response. Trace the JWT claims mapping, then verify that top-level nca_id populates ownerNcaId while authorizations.ncaId remains the existing ncaId value; done means the validation result matches the described managed-environment response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100