SonatypeFortifyBundle-5.4.2

Changelog

• Added support for fetching projects using pagination from Fortify SSC

SonatypeFortifyBundle-5.4.1

Changelog

• Fixed an issue where expired waivers caused syncronization to fail
• Fixed an issue where auto-waivers caused syncronization to fail

SonatypeFortifyBundle-5.4.0

Changelog

• Added a new endpoint for ad‑hoc synchronization by scanId

SonatypeFortifyBundle-5.3.0

Changelog

• Converted the iqWebhook endpoint to an asynchronous model to improve stability

SonatypeFortifyBundle-5.2.1

Changelog

• Prevented redundant artifact uploads when no missed reports were found in the history

SonatypeFortifyBundle-5.2.0

Changelog

• Fixed a bug that caused redundant artifacts
• Added support for Golden Versions, the non-breaking upgrade resolving policy violations for the component and its dependencies

SonatypeFortifyBundle-5.1.3

Changelog

• Fixed an issue where an older report was uploaded to Fortify SSC. The sync service now correctly prioritizes and only uploads the latest available report
• Added the Sonatype Policy Name to the violation detail view

SonatypeFortifyBundle-5.1.2

Changelog

• Fixed an issue where the expected scan report was not being synchronized if the most recent one was an identical report generated by continuous monitoring

SonatypeFortifyBundle-5.1.1

Changelog

• Fixed issue where sync service did not terminate as expected when the killProcess flag was set to true
• Added support for fortifyApplicationId when using the startScanLoad endpoint

SonatypeFortifyBundle-5.1.0

Changelog

• Fortify Application ID can now be used to map JSON instead of the application name
• Added support for synchronizing all violation categories, not only security
• Uploads of reports generated by continuous monitoring will be skipped if the data is identical to the previously uploaded report
• Fortify Audit Details are now clickable links for Fortify versions 23.0 and later
• Included license information for the report in the synchronized artifact. This can be configured via the include.license.information property