Azure / Azure/data-api-builder
Authorization Policy vNext -> Request Policies
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 372
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 9
Description
M1/1.5 met the requirement of adding support for Database Policies. This next iteration is to apply policies at the request level: policy resolution does not result in database query predicates, and instead checks the policy against claims present in the user's token and makes a allow/deny decision.
Per RFC request policy: defines a rule that will be checked before sending any request to the database
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 with the linked RFC's policy expression language section and compare the request-policy requirements with the existing database-policy support described in the issue. Trace how a request reaches the database and identify where token claims would be evaluated; done means an allow/deny decision occurs before the database request without adding query predicates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100