...
- apiKey - unique identifier of the organization. It can be retrieved from the 'Integrate' page in your WhiteSource account
- userKey - unique identifier of the user, and it is optional. It can be generated from the 'Profile' page in your WhiteSource account. With the user key WhiteSource recognize who runs the scan.
- wss.url - enable the relevant URL according to your organization's WS 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 tree versions of wss.url:
- #wss.url=https://saas.whitesourcesoftware.com/agent
- #wss.url=https://app.whitesourcesoftware.com/agent
wss.url=https://app-eu.whitesourcesoftware.com/agent (our WhiteSource run under this url)
- productToken - identified what product we scan. After we add a new product, productToken First, create a new product.
To create a new product do the following:From the menu bar, select Products > New Product. The Create New Product screen is displayed.
Enter your product name, and click Create.
ProductToken can be retrieved from the 'Integrate' page in your WhiteSource account. In the product, we can define many projects.
- projectToken - after running the scan, output goes to the project. ProjetToken can be retrieved from the 'Integrate' page in your WhiteSource account. Best After running the scan, the output goes to the project.
Best practices - WhiteSource 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 WhiteSource. If names or versions change rapidly, then use
...
the 'projectToken' and 'productToken' of the existing WhiteSource counterparts.
In section Polices:
...