Bad permission definitions
Description
CSP Request Details
None
CSP Rejection Details
None
Potential Workaround
None
Attachments
2
relates to
Checklist
hideTestRail: Results
Activity
Show:

Mike TaylorApril 26, 2017 at 1:57 PM
Assigning to Kurt, just to get this kickstarted.

Mike TaylorApril 24, 2017 at 11:36 AM
And I also attached the output of perm-tree.js
on the new available permissions, in case it helps to visualise what's wrong.

Mike TaylorApril 24, 2017 at 11:35 AM
I attached the complete set of available permissions, as returned from http://localhost:9130/perms/permissions?length=1000 – hope it's helpful.
Done
Details
Assignee
Kurt NordstromKurt NordstromReporter
Mike TaylorMike TaylorPriority
P3TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee

Reporter

Priority
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created April 24, 2017 at 11:33 AM
Updated November 12, 2018 at 2:23 PM
Resolved May 8, 2017 at 1:33 PM
As I've been analysing the set of permissions that are available in folio-backend-auth v0.11.0, I have found a few errors. Specifically:
login.all includes as a sub-permission login.item.delete, but there is no such permission.
users-bl.create includes as a sub-permission perms.users.create, but there is no such permission.
There is a permission called login.item delete (with a space), which should presumably by login.item.delete
I don't know where these various permissions come from, so I don't know who to assign this to. I am giving it to Kurt initially, to get the ball rolling; but, Kurt, feel free to reassign if someone else should be handling this.