Configure the Veracode Integration for CA Agile Central

Ticketing Systems

Before you begin

Before you can use the Veracode Integration for CA Agile Central, you must have the following installed in your environment:
  • Java 1.8
  • Project administrator rights in a CA Agile Central account

About this task

This topic describes the necessary configurations for using the Veracode Integration for CA Agile Central. For information on additional customizations available for the integration, refer to the veracode2agilecentral_config.xml customization table.

To configure your local instance of the integration:

Procedure

  1. Go to https://tools.veracode.com/integrations/AgileCentral/bin/veracode-agilecentral-integration.zip and download the ZIP file.
  2. Extract the ZIP file and paste the following files to a folder in your local environment:
    • scheduler.properties
    • veracode2agilecentral.xsl
    • veracode2agilecentral_config.xml
    • veracode-agilecentral-integration.jar
    This folder is referred to as your root folder in this document.
  3. Open veracode2agilecentral_config.xml for editing.
  4. Locate the <mapping> node and update the following elements with your appropriate information:
    mapping node
    • <veracodeappname> - Optional. The application name as it appears in the Veracode Platform.
    • <veracodeappid> - The application ID as it appears in API calls.
      Note: To find the ID for an application, open the applications page in the Veracode Platform and copy the second string of integers in the URL. app id
    • <agilecentralprojectname> - Optional. The project name as it appears in CA Agile Central.
    • <agilecentralprojectid> - The numeric value in the project ID for the project in CA Agile Central.
  5. If you are using the integration with multiple applications, copy the <mapping> node, paste it directly below the existing node, and repeat step 4 for each application.
  6. Locate the <veracode> node and update the following elements with your appropriate information:
    veracode node
    • <api_id> - The API ID for your Veracode Platform account.
    • <api_key> - The API secret key for your Veracode Platform account.
  7. Locate the <agilecentral> node and update the following elements with your appropriate information:
    agilecentral node
    • <url> - The URL of the CA Agile Central instance to which you want to connect. In most cases, this value is https://rally1.rallydev.com.
    • <api_key> - API key for your CA Agile Central account.
  8. Edit the state_field, severity_field, priority_field, and resolution_field values in the configuration XML and XSL files to match your CA Agile Central configuration.
    1. To perform these edits, locate the appropriate node in veracode2agilecentral_config.xml, for example <state_field>.
    2. Update the elements in that node to match the values in your CA Agile Central project. The opening and closing tags for each element must match the value of the field, excluding non-alphabetic characters. For example, if one of the available states for tickets in your CA Agile Central project is Resolved, enter <resolved>Resolved</resolved> within the <state_field> node.

    3. Open veracode2agilecentral_config.xsl and edit the appropriate mapping to match the update you made in veracode2agilecentral_config.xml. For example, if you configured <resolved>Resolved</resolved> within the <state_field> node in the XML file, locate the state_field mappings in the XSL file and update the appropriate mapping to select resolved.

    4. Perform these steps for each value in the state_field, severity_field, priority_field, and resolution_field that you need to update.
  9. Create new custom fields in your CA Agile Central project for Veracode flaw IDs, mitigation actions, mitigation comments, mitigation history, and product hierarchy IDs. For instructions on how to create custom fields, refer to CA Agile Central documentation.
    Note: This action requires workspace administrator rights in CA Agile Central.
  10. Configure the mappings associated with these new fields in the configuration XML file.
    1. In veracode2agilecentral_config.xml, locate the <customfield> node and enter the field names you created within the appropriate tags.

    2. Save and close veracode2agilecentral_config.xml and veracode2agilecentral_config.xsl.