Fix policies hierarchy and CWT.sub checking
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 16
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Currently service_definition_auth and platform_definition_auth are per unique per ADNS instance.
Setting platform_definition and service_definition is authorized with respective _auth policies with no use of cwt claims, and is per service/platform name.
Initial assumption was to make both service_definition_auth and service_definition per service_name, and platform_definition_auth + platform_definition unique per instance. Then new service_definition_auth is checked against itself, same for platform_definition_auth.
Before doing, the value of cwt.sub to be defined for
-
service_definition_auth -
service_definition -
platform_definition_auth -
platform_definition
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 tracing the four named policy entries: service_definition_auth, service_definition, platform_definition_auth, and platform_definition. Determine how their per-instance or per-service/platform scope relates to cwt.sub checks; done means the hierarchy and cwt.sub values are explicitly agreed and consistently applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100