As described here, you can add or remove a scanning tool from your local configuration of Code Sight.

To add a scanning tool that has not yet been authenticated

To add a scanning tool in Eclipse, a JetBrains IDE (including IntelliJ), or Visual Studio, use the Status view → Products and Licenses panel. In VS Code, this is a tab that is accessible from the STATUS view.

Click the tile for the scanning tool that is not yet active—or in VS Code, click the tool’s Enable button.

Code Sight displays the Authentication Required page once again, so you can add your account name, your password, and (if the tool does not run standalone) the URL of the server that the tool will use.

To remove an engine so that Code Sight stops running it

To remove a scan engine from Code Sight, you need to remove the engine from your system.

  1. Close the development environment (IDE) from which you run Code Sight.
  2. Navigate to the directory where it was installed, and delete the directory/folder that contains the Black Duck software-integrity engine you no longer want to use.

    The default installation location depends on the operating system you are using. See the following table:

    Platform

    Location of directory/folder
    where engines are installed

    Directory/folder
    for the particular engine
    Linux or Mac

    /Users/<username>/
        .blackduck/desktop/
            controller/installedtools/

    		 blackduck/
    coverity-analysis/
    sigma/
    Windows

    C:\Users\<Username>\AppData\Roaming\
        BlackDuck\desktop\
            controller\installedtools\

    		 blackduck\
    coverity-analysis\
    sigma\

    Some sites install the desktop/ folder in a custom location. If you do not see it in the default location, consult your system administrator.

  3. Restart the IDE.
    Now the Code Sight interface should indicate that you are connected only to the server for the engine that is still installed on your system.