Veracode Integrations Past Release Notes

Veracode Release Notes

View the list below for highlights of previous releases.

March 24, 2020

Veracode Azure DevOps Extension Removes Basic Authentication
The Veracode Azure DevOps Extension version 3.0.0 removes basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.

February 21, 2020

Veracode Greenlight for Eclipse Supports Eclipse IDE 2019-12
Veracode Greenlight for Eclipse version 2.8.6 adds support for Eclipse IDE 2019-12 (4.14).

February 14, 2020

Veracode Greenlight for IntelliJ Supports IntelliJ IDEA 2019.3
Veracode Greenlight for IntelliJ version 1.5.1 adds support for IntelliJ IDEA Ultimate and Community 2019.3.

February 12, 2020

Veracode Jenkins Plugin Removes Basic Authentication
The Veracode Jenkins Plugin version 20.2.6.1 removes basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.

January 31, 2020

Veracode Static for Eclipse Supports Eclipse 2019-09
Veracode Static for Eclipse version 3.4.0 replaces the Veracode Eclipse Plugin. This version adds support for Eclipse 2019-09. It also adds support for Java Runtime Environment (JRE) 11 and 13.

You can no longer use basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.

January 24, 2020

Veracode Static for IntelliJ Supports IntelliJ IDEA 2019.3
Veracode Static for IntelliJ version 3.0.0 replaces the Veracode IntelliJ Plugin. This version supports IntelliJ IDEA Ultimate and Community 2017.x to 2019.3. It also adds support for Java Runtime Environment (JRE) 11 and 13.

You can no longer use basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.

January 23, 2020

Updated Veracode Integration for Jira
The Veracode Integration for Jira version 3.22.0 includes these updates:
  • Removes support for basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.
  • Enhances Jira logging, so that you can more easily read the logs.
  • Improves the performance of importing findings from the Veracode Platform to Jira using custom fields.

January 17, 2020

Veracode Static for Visual Studio Supports Visual Studio 2019
Veracode Static for Visual Studio version 4.0.0.1 replaces the Veracode for Visual Studio Extension. This version supports Visual Studio 2015, 2017, and 2019. In Visual Studio 2015 and 2017, the name of the top-level Veracode menu is now Veracode Static. In Visual Studio 2019, the Veracode Static menu appears under the Extensions menu.

You are required to configure an API credentials file, which you use to provide your Veracode API ID and key credentials to Veracode Static for Visual Studio.

January 8, 2020

Updated Veracode Integration for Jira Cloud
The Veracode Integration for Jira Cloud version 3.2.0 includes these updates:
  • Adds a new Veracode Integration Severity Mappings page in the Jira Cloud interface for mapping severities from the Veracode Platform to your customized priorities in Jira Cloud.
  • On the Veracode Integration Field Mapping page in the Jira Cloud interface, the Veracode Platform column adds these new options:
    • A Description (overwrite) option to have the content from a selected Veracode Platform field overwrite the Description field in Jira Cloud upon import. If the selected Veracode Platform field is empty, the mapping erases the contents of the Description field in Jira Cloud.
    • An option for mapping Veracode SCA component paths.
  • Removes basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.