-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add app_id to roles schema #108
Labels
enhancement
New feature or enhancement of existing functionality
T1h
Time Estimate 1 Hour
technical
A technical issue that requires understanding of the code, infrastructure or dependencies
Comments
nelsonic
added a commit
that referenced
this issue
Sep 11, 2020
11 tasks
At present the roles listing looks like this: http://localhost:4000/roles Next: add |
nelsonic
added a commit
that referenced
this issue
Sep 11, 2020
Roles as viewed by Admin: http://localhost:4000/roles (showing two custom roles) |
Marginally better layout: http://localhost:4000/roles/1/edit |
nelsonic
added a commit
that referenced
this issue
Sep 11, 2020
This was referenced Sep 11, 2020
nelsonic
added a commit
that referenced
this issue
Sep 13, 2020
Added |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or enhancement of existing functionality
T1h
Time Estimate 1 Hour
technical
A technical issue that requires understanding of the code, infrastructure or dependencies
In order to make RBAC useful we need to be able to create roles for Apps.
And when a
new
person
joins an App, they need to be assigned a role specific to that App.Todo
app_id
field toroles
schema./approles/:client_id
should return the list of roles asJSON
where
:client_id
is the first half of theAUTH_API_KEY
(similar to howauth_plug
handles auth).and "default" roles created by
seeds.exs
Get List of Roles for App #110app_id
toconn.assigns.person
so that we know whichapp
the person authenticated with. Related: https://github.com/dwyl/auth_plug/issues/24The text was updated successfully, but these errors were encountered: