OpenConext / OpenConext/OpenConext-Invite
Limit API keys to single SP's
Open
Nobody has claimed this yet.
api
needs refinement
- Dominant language
- Java
- Stars
- 6
- Forks
- 7
- Avg merge
- 12h 24m
- Merged PRs (30d)
- 11
Description
See CXT-84026
It is useful to scope API key's to a single application, eg when a application is hosted or operated by a 3rd party.
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 API-key implementation and the linked CXT-84026 request; the issue names no files or tests. Identify the entry points and data model involved in associating keys with applications or service providers. Done means an API key can be limited to one service provider and that behavior is covered by appropriate verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100