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
To start with the obvious, have you confirmed that the Fortify SSC ScanCentral controller is up and listening at this endpoint?
You should able to open this URL in a browser and see the following message confirming that it is responding...
Fortify CloudScan Controller