Child pages
  • IBM Security AppScan Source Scanner Plugin

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


For additional reading on the login command, please see IBM's documentation:

Plugin Configuration

  1. From the Jenkins homepage, click Manage Jenkins and then Configure System
  2. Scroll down the page and locate the section titled AppScan Source
  3. Click Add AppScan Source
  4. Fill out the AppScan Source form
    1. AppScan Source Name: A name for this instance of AppScan Source. This is just to help manage environments that may have multiple installations
    2. AppScan Source Installation Directory: The path to the installation directory. Note: the default value is C:\Program Files (x86)\IBM\AppScanSource
  5. Scroll to the bottom and locate the section titled AppScan Source Configuration and fill out the form
    1. AppScan Enterprise Hostname/Domain Name: The host name of your AppScan Enterprise server
  6. Login Token File Path: This is the path to the login token generated above. Default path is C:\Users{user}\.ounce\ouncecli.token
  7. Click Save

Using the plugin

  1. Create a new job or access an existing job
  2. Select "Configure"
  3. Select "Add build step" and select "Run AppScan Source"
  4. Complete the fields that appear:
    1. AppScan Source installation will show the name you provided for the installation on the global configuration screen. If you have not added an installation, please go the the Jenkins Configure System link under Manage Jenkins. If you only have one installation configured, the installation should be selected for you. If you plan to execute AppScan Source on multiple Jenkins nodes, you may need to configure multiple installation paths.
    2. Disable scan should be unchecked if you wish the scan to run
    3. Accept SSL Errors should be checked if you have not created a trusted certificate for your AppScan Source installation. In an Enterprise environment, this should not be checked, since you should be using a trusted certificate.
    4. Scan Workspace Directory is where scan artifacts, like WAFL and staging files will be placed. Scan results (.ozasmt file) will also be placed in this directory.
    5. Application file should point to a PAF or SLN file to scan.
  5. Click Save at the bottom
  6. Run the job.


This version of the plugin was tested with Jenkins 1.651.1 and IBM Security AppScan Source 9.0.3. Plugin should work with any version of AppScan Source 9.0.0 or newer.


Support automated publishing of scan results to AppScan Enterprise.


Execute application scans with IBM Security AppScan Source