RBAC (or other way of segmentation) of access to APIML services
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Is your feature request related to a problem? Please describe.
Some admins of the APIML may want to set up permissions such that some users can only access the API catalog and some can access API Catalog and the Metrics Service.
Describe the solution you'd like
A segmentation of authorization such that some users can access API Catalog without being authorized to access the Metrics Service.
Describe alternatives you've considered
Keep it the same as it is now, which is all or nothing auth.
Additional context
Add any other context or screenshots about the feature request here.
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
The issue names no files, tests, or entry points. Start by mapping how APIML currently authorizes access to the API Catalog and Metrics Service, then define the permission boundaries and configuration needed for separate access. Done means users can access the Catalog without Metrics Service authorization, while existing all-or-nothing behavior is covered or intentionally changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100