Cadet 1st Class
Cadet 1st Class
248 views

Jenkins fails with fortify central scan

Jump to solution

Good afternoon folks, have any of you already gotten this flaw in Jenkins when using central scan and sensor?

 

Iniciado pelo usuário admin
Running as SYSTEM
Construindo remotamente em Jenkins_224 no workspace C:\Jenkins\workspace\Cabrito
Fortify Jenkins plugin v 20.2.34
Running remote translation and scan.
Fortify Jenkins plugin v 20.2.34
Performing Fortify remote analysis
Found executable: C:\Tools\SCA\bin\scancentral.bat
[Cabrito] $ C:\Tools\SCA\bin\scancentral.bat -sscurl http://192.168.10.21:8180/ssc -ssctoken 014a10a7-ad87-47b5-bff7-3b07d0237ee5 start -bt mvn -bf C:\Users\Adminidtrator\Downloads\WebGoat-devolop\WebGoat-develop\pom.xml -pool 14439f03-4dba-4963-811d-6b2218ab2b18 -upload -application Cabrito -version 1.0 -uptoken 014a10a7-ad87-47b5-bff7-3b07d0237ee5
Log files will be stored in "C:\Users\Administrator\AppData\Local\Fortify\scancentral\log" directory.
Retrieving controller URL...
Verifying controller URL...
Initializing client authorization token...
Controller at http://192.168.10.27:8180/scancentral-ctrl did not respond - either is not available or authentication failed
Shutting down with errors. Please see log for details.
Fortify remote analysis completed with exit code: 1
ERROR: Step ‘Fortify Assessment’ failed: Fortify remote analysis execution failed.
Finished: FAILURE

Thank you very much in advance

0 Likes
1 Solution

Accepted Solutions
Cadet 1st Class
Cadet 1st Class

Hello, I managed to solve the problem, it was a client authentication failure that was not allowing the connection

View solution in original post

2 Replies
Vice Admiral Vice Admiral
Vice Admiral

Hi Eduardo,

To start with the obvious, have you confirmed that the Fortify SSC ScanCentral controller is up and listening at this endpoint?

http://192.168.10.27:8180/scancentral-ctrl

You should able to open this URL in a browser and see the following message confirming that it is responding...

Fortify CloudScan Controller

 

0 Likes
Cadet 1st Class
Cadet 1st Class

Hello, I managed to solve the problem, it was a client authentication failure that was not allowing the connection

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.