Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement access control config client to setup default permissions in petstore #147

Open
kushagra189 opened this issue Oct 1, 2022 · 1 comment
Labels
priority: medium Medium priority status: blocked Something prevents progress type: maintenance Related to general repository maintenance workload: days Likely takes days to resolve
Milestone

Comments

@kushagra189
Copy link
Contributor

This issue is blocked by #146.
Once the client is implemented, we need to use that client in the petstore example to automatically set the permissions of a newly created resource such that the creator becomes the owner of the resource, i.e., they should be allowed to read (GET /petsandGET /pets/{id}) and delete (DELETE /pets/{id}`) the resource.

@kushagra189 kushagra189 self-assigned this Oct 1, 2022
@kushagra189 kushagra189 added priority: high High priority status: blocked Something prevents progress type: maintenance Related to general repository maintenance workload: days Likely takes days to resolve labels Oct 1, 2022
@kushagra189
Copy link
Contributor Author

#157

@uniqueg uniqueg added priority: medium Medium priority and removed priority: high High priority labels Dec 2, 2023
@uniqueg uniqueg added this to the v1.0.0 milestone Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium Medium priority status: blocked Something prevents progress type: maintenance Related to general repository maintenance workload: days Likely takes days to resolve
Projects
Status: Todo access control
Development

No branches or pull requests

2 participants