Enforce permissions in the UI
Description
Environment
Potential Workaround
is blocked by
is duplicated by
Checklist
hideTestRail: Results
Activity
Khalilah Gambrell July 9, 2019 at 9:56 PM
The only open issue is tied to restricted fields. I unassigned that open issue as it might be addressed in the future under a UXPROD feature
Mike Taylor March 17, 2017 at 4:54 PM
Eight of the eleven blockers for this umbrella are done. Of the three remaining blockes, two are themselves blocked on other work, and the last (https://folio-org.atlassian.net/browse/LIBAPP-147#icft=LIBAPP-147) I don't want to do before I've discussed it with the person whose code I will be making structural changes to. So this has gone as far as it can go at the moment.
Mike Taylor March 12, 2017 at 6:37 PM
I've generalised the implementations of https://folio-org.atlassian.net/browse/LIBAPP-138#icft=LIBAPP-138 and https://folio-org.atlassian.net/browse/LIBAPP-146#icft=LIBAPP-146 into a utility <IfPermission> component, presently within the Users UI module but ready to be moved into stripes--components. To be used like this:
<IfPermission {...this.props} perm="users.create">
<Button fullWidth onClick={this.onClickAddNewUser}>New user</Button>
</IfPermission>Mike Taylor March 10, 2017 at 1:12 PM
Note to self: the overview document on FOLIO authentication, permissions and authorisation is https://github.com/folio-org/okapi/blob/master/doc/security.md
Details
Details
Assignee
Reporter
Priority
P3
(Umbrella to block all the LIBAPP issues that describe specific permissions.)