Issues
- Sensitive data in logs cleanupMODCAMUNDA-33
- Upgrade org.jruby.jruby to 9.4.11.0.MODCAMUNDA-32Resolved issue: MODCAMUNDA-32Kevin Day
- Upgrade org.apache.commons.commons-text to 1.13.0MODCAMUNDA-31Resolved issue: MODCAMUNDA-31Kevin Day
- Upgrade com.googlecode.libphonenumber.libphonenumber to 8.13.54.MODCAMUNDA-30Resolved issue: MODCAMUNDA-30Kevin Day
- Upgrade Ojdbc10 to Ojdbc11 21.17.0.0.MODCAMUNDA-29Resolved issue: MODCAMUNDA-29Kevin Day
- Upgrade org.marc4j.marc4j to 2.9.6MODCAMUNDA-28Resolved issue: MODCAMUNDA-28Kevin Day
- Upgrade graalvm polyglot to 24.1.2MODCAMUNDA-27Resolved issue: MODCAMUNDA-27Kevin Day
- Confirm works under spring-boot 3.4.x and fix any regressions or deprecations.MODCAMUNDA-26Resolved issue: MODCAMUNDA-26Kevin Day
- Investigate and consider rewriting FtpDelegate to use Apache Commons Net instead of Commons VFS2MODCAMUNDA-25
- Use hadoop-hdfs-client 3.4.1 to fix XML External Entity (XXE) InjectionMODCAMUNDA-24Resolved issue: MODCAMUNDA-24Kevin Day
- Use jsch@0.2.15 to fix Authentication Bypass by Capture-replayMODCAMUNDA-23Resolved issue: MODCAMUNDA-23Kevin Day
- Readme is out of date.MODCAMUNDA-22Resolved issue: MODCAMUNDA-22
- Upgrade camunda and graalvm for Ramsons (R1 2025)MODCAMUNDA-21Resolved issue: MODCAMUNDA-21Kevin Day
- Remove the build and run Dockerfile.MODCAMUNDA-20Resolved issue: MODCAMUNDA-20Kevin Day
- Mod Inventory related permissions need to be removed.MODCAMUNDA-19
- Mod Camunda should be deployable on TAMU InfrastructureMODCAMUNDA-18Resolved issue: MODCAMUNDA-18
- [SPIKE] A workflow should be able to be triggered by a message correlation from a kafka message queueMODCAMUNDA-17
- Mod Camunda should support the kafka messaging instead of active mqMODCAMUNDA-16Resolved issue: MODCAMUNDA-16Kevin Day
- Update module to utilize new spring-module-core setting: tenant.recreate-default-tenantMODCAMUNDA-15Resolved issue: MODCAMUNDA-15Kevin Day
- Mod Camunda should support the InputTaskMODCAMUNDA-13Resolved issue: MODCAMUNDA-13Kevin Day
- Enable API-related GitHub WorkflowsMODCAMUNDA-12
- DatabaseQueryDelegate uses simple CSV/TSV and simple JSON encoding.MODCAMUNDA-11
- FileTask Delegate target property - not functioning properlyMODCAMUNDA-14Kevin Day
- The deleting deployments should not throw an exception if the deployment is already deleted.MODCAMUNDA-10Resolved issue: MODCAMUNDA-10Kevin Day
- The delete deployment method should pass true in the cascade parameterMODCAMUNDA-9Resolved issue: MODCAMUNDA-9Kevin Day
- Improve unit test coverageMODCAMUNDA-7
- Create proxy endpoints for all used camunda rest endpointsMODCAMUNDA-5
- Refactor camunda paths and permissions to workflow-engine in mod-camunda’s module descriptorMODCAMUNDA-4
- Clean up current trailing slash work-aroundMODCAMUNDA-3Resolved issue: MODCAMUNDA-3Kevin Day
- Migrate project to the spring-way dependencyMODCAMUNDA-2Resolved issue: MODCAMUNDA-2
- Upgrade to Spring Boot 3MODCAMUNDA-1Resolved issue: MODCAMUNDA-1Kevin Day
31 of 31
It is necessary to review the information available in the module logs. Personally Identifiable Information (PII) that directly (explicit user personal data, financial information, etc.) or indirectly (references to files in S3 or local files containing personal information) allows the identification of a user must be removed. If removal is not possible, the information should be masked. Among the PII, the following should be removed (if applicable):
Direct Identifiers (explicitly identify an individual):
Full name
Social Security Number (SSN)
Passport number
Driver’s license number
Email address
Phone number
Physical address
Indirect Identifiers (can identify an individual when combined with other information):
Date of birth
IP address
Geolocation data
Employment information
Medical records
Financial data (e.g., credit card details)
Acceptance criteria:
All PII is not present in the module logs based on logs visual review.