You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As an admin usher user, I would like to have APIs available to manage Permissions. Some of the APIs are already implemented, this issue should complete the missing APIs.
API Design
Status
URL
Auth
Params
Notes
✅
GET /clients/client_id/permissions
bearerAdminAuth
client_id optional: query param
List Permissions
TODO
GET /clients/client_id/permissions/:permission_key
The source files should be placed in the src/api_endpoints/permissions folder.
For the Create Permission API, the clientkey attribute should be optional
The Permission object should return both client key and the client id attributes
Questions
Should the PATCH API to update a permission allow for updating a client key? I can see arguments for either case. Maybe we say no to start to keep things simple? As if you want to "move" a permission from one client to another is really not a common use case , or one we want to support.
The text was updated successfully, but these errors were encountered:
Feature Overview
Is your feature request related to a problem? Please describe.
As an admin usher user, I would like to have APIs available to manage Permissions. Some of the APIs are already implemented, this issue should complete the missing APIs.
API Design
/clients/client_id/permissions
/clients/client_id/permissions/:permission_key
/clients/client_id/permissions
/clients/client_id/permissions/:permission_key
/clients/client_id/permissions/:permission_key
Implementation Notes
src/api_endpoints/permissions
folder.clientkey
attribute should be optionalQuestions
The text was updated successfully, but these errors were encountered: