Issues
- Review and cleanup Module Descriptors for mod-audit-filterMODAFILT-13Resolved issue: MODAFILT-13Natalia Zaitseva
- Upgrade mod-audit-filter to Java 11, or consider archive the repositoryMODAFILT-12Resolved issue: MODAFILT-12David Crossley
- Use JVM features to manage container memoryMODAFILT-11Resolved issue: MODAFILT-11David Crossley
- Re-assess the container Memory allocation in default LaunchDescriptorMODAFILT-10
- Spike: familiarization with mod-audit, mod-audit-filterMODAFILT-9Emma Boettcher
- Capture check in in audit appMODAFILT-8Resolved issue: MODAFILT-8Emma Boettcher
- Capture check out in audit appMODAFILT-7Resolved issue: MODAFILT-7Emma Boettcher
- Use filter type=request-logMODAFILT-6Resolved issue: MODAFILT-6Hongwei Ji
- No need to try to turn the body into a Json if the contentType is not application/jsonMODAFILT-5Resolved issue: MODAFILT-5Hongwei Ji
- Release 0.0.2MODAFILT-4Resolved issue: MODAFILT-4Hongwei Ji
- Do not reply on mod-auth-token moduleMODAFILT-3Resolved issue: MODAFILT-3Hongwei Ji
- Add mod-audit-filter to daily folio/testing Vagrant boxMODAFILT-2Resolved issue: MODAFILT-2Hongwei Ji
- Create and release the first version mod-audit-filterMODAFILT-1Resolved issue: MODAFILT-1Hongwei Ji
13 of 13
Review and cleanup Module Descriptors for mod-audit-filter
Won't Do
Description
Environment
None
Potential Workaround
None
Checklist
hideDetails
Details
Assignee
Natalia Zaitseva
Natalia ZaitsevaReporter
Natalia Zaitseva
Natalia ZaitsevaLabels
Priority
P4
Release
Ramsons (R2 2024)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created September 4, 2024 at 10:27 AM
Updated September 30, 2024 at 7:54 AM
Resolved September 30, 2024 at 7:54 AM
Activity
Show:
Natalia ZaitsevaSeptember 30, 2024 at 7:54 AM
module is deprecated - https://github.com/folio-org/mod-audit-filter
Natalia ZaitsevaSeptember 30, 2024 at 7:54 AM
Hey , @Tetiana Gusar, yes, it was mistakenly assigned to the Volaris team.
Tetiana GusarSeptember 25, 2024 at 3:13 PM
Hi, I guess this ticket was added to Volaris by mistake. Please reassign it to the proper team.
To support automatic capabilities creation and keep FOLIO permission usage consistent, it is suggested that all module descriptors be reviewed and inconsistencies in permission namings and usage be fixed.
https://github.com/folio-org/folio-module-descriptor-validator can help teams with finding such problems in the module descriptor.
If the module is not a java based - https://github.com/folio-org/folio-module-descriptor-validator/blob/master/scripts/module-descriptor-batch-validator/README.md
Permission naming convention for renaming - https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/156368925/Permissions+naming+convention
How to rename a permission:
https://folio-org.atlassian.net/wiki/spaces/TC/pages/5055284/DR-000014+-+Migration+of+Static+Permissions+Upon+Upgrade
https://github.com/folio-org/okapi/blob/master/doc/guide.md#permissions-and-the-_tenantpermissions-interface
Rules for Module Descriptor:
Permission name according to the convention
One permission can be used to protect only one endpoint
Endpoint should be protected by 0-1 permissions
Permission with sub permissions(Permission set) can’t be used for endpoint protection
Scope:
Add plugin to the modules pom file and run build
Fix problems in module descriptor according to the Permission naming convention or rules
If module is not a java based - run local scripts and fix module descriptor