ChilliCream / ChilliCream/graphql-platform
how to apply authorization policy on some columns or navigations to use projection with ef core
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.8k
- Forks
- 810
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 98
Description
Is your feature request related to a problem?
when have multiple roles in system and every role has dedicated access to some fields and we want to automatically apply roles or something like that (claims) for projection
example
student => fields: id , name , grade
we have 3 roles
role1 => can just access to student names
role2 (teacher) => can access to name and grade of all students
role3 (student) => can access to name of all students but just access to grade of himself (student id is a claim and just access to grade of student where student.Id== studentId( in claims)
is there any way to support this issue in current version of hotchocolate?
The solution you'd like
nothing
Product
Hot Chocolate
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 by reviewing Hot Chocolate's current authorization and projection capabilities, including how claims or roles could affect fields and navigations. Use the student, teacher, and role examples in the issue to define the expected access rules. Done means determining whether the current version supports this behavior or documenting the scope of a feature needed to support it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100