Securing APIs by default
Description
Environment
None
Potential Workaround
None
defines
Checklist
hideTestRail: Results
Activity
Show:
Marc Johnson April 29, 2020 at 3:59 PM
Thanks
Oleksii Kuzminov April 29, 2020 at 8:01 AM
We will deal with it
Ann-Marie Breaux April 28, 2020 at 4:35 PM
Hi your call - what do you think?
Marc Johnson April 28, 2020 at 4:29 PM
As the json schemas endpoint is something that you added to mod-inventory-storage, could this be picked up by FoliJet?
Done
Details
Details
Assignee
Ruslan Lavrov
Ruslan LavrovReporter
Hongwei Ji
Hongwei JiLabels
Priority
P2Story Points
0.5
Sprint
None
Development Team
Folijet
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created April 24, 2020 at 11:34 PM
Updated June 4, 2020 at 6:48 AM
Resolved May 14, 2020 at 4:55 PM
TestRail: Cases
TestRail: Runs
Per , all public APIs should be protected by default. That means field permissionsRequired is required when defining non-system APIs in the handlers section of module descriptor. If there is a strong technical reason that an API cannot be protected, for example, /authn/login, use *"permissionsRequired" : [ ]* to make it explicit. Note it is OK to use *"permissionsRequired": [ ]* for two APIs //ramls and //jsonSchemas provided by RMB.
Please fix following APIs in this module