Page History

...

This document describes the product scanning scenario. It is not expected that endusers would be required to end-users set up their project in Mend themselves. The work described here is part of GEANT Mend setup-the GEANT Software Composition Analysis (SCA) assistance service. This information is published to provide a deeper understanding of the workflows and functioning of Mend and capture its key elements.

Firstmost, it is necessary to get acquainted with Unified Agent (UA).

Unified Agent (UA) - Overview

The Unified Agent is a Java command-line tool that scans directories' open source components for vulnerable libraries and license complications , and displays the results in the Mend web application. The Unified Agent works the following way: directories are scanned to identify the open-source components, whereupon the Unified Agent checks each new component against organizational policies (note that no source code is scannedshared - only descriptive information is sent to Mend).

At the end of the Unified Agent's scan, it aggregates the information and uploads it to the Mend web application, where it is presented in an Organization/Product/Project hierarchy, enabling the user to view and analyze the scan results. Additionally, an informative report of the results is generated in HTML and JSON formats, located in the 'Mend' folder. This folder is created in the directory where the Unified Agent ran.

Prerequisites

Java JDK/JRE installation is required in order to run the Unified Agent. The following versions of Java are supported:

...

Additionally, depending on what you are scanning, ensure that the relevant build tools, package managers, etc. are installed. An overview of project types and corresponding project managers is given here.

Installation

1. Download the Unified Agent .jar file from here.
2. Download the default configuration file from here and  and place it in the same directory as the Unified Agent jar file. 

Configuring the Unified Agent

Enter the following parameters in the configuration file:

• apiKey - unique identifier of the organization. It can be retrieved from the 'Integrate' page in your Mend account 
• userKey - unique identifier of the user, and it is optional. It can be generated from the 'Profile' page in your Mend account. With the user key key, Mend recognize who runs the scan.
• wss.url - enable the relevant URL according to your organization's WS Mend Server URL from your Profile page on the Server URLs panel (additionally, it can be found in the Integrate tab). Then, add the agent path. in the config file. There are three versions of wss.url:
  • #wss.url=https://saas.Mendsoftwarewhitesourcesoftware.com/agent
  • #wss.url=https://app.Mendsoftwarewhitesourcesoftware.com/agent

  • wss.url=https://app-eu.Mendsoftwarewhitesourcesoftware.com/agent (our Mend run under this url)
    

• productToken - identifies the product to be scanscanned. First, you need to create a new product.
  To create a new product do the following: 

  1. From the menu bar, select Products > New Product. The Create New Product screen is displayed. 

  2. Enter the product name, and click Create.

...

Best practices - Mend recommends placing the project and product names in the configuration file (versions are optional). This is preferable for the first-time setup as it automatically creates a new project and product in Mend. If names or versions change rapidly, then use the projectToken and productToken of the existing Mend counterparts.

In the section Polices:

• checkPolicies - checkPolices=false;  policies are not being checked, as we don't have policies for now

...

In the section Package Manager Dependency resolversResolvers, there are are all dependencies that UA can scan (#resolveDependencies=false); they all are comments, so all will be scanned by UA. In GÉANT there are many different projects with many technologies and languages, so it would be safer to scan all dependencies.

Running the Unified Agent from the Command Line (Scanning Procedure)

To run the Unified Agent from the command line, execute the following command on the machine where your codebase is located:

...