search

jenkinsci / fortify-plugin

Fortify Jenkins plugin
https://plugins.jenkins.io/fortify
Other
23 stars 31 forks source link

Plugin generated command is missing ssctoken and uptoken #15

Closed fabitamas closed 4 years ago

fabitamas commented 4 years ago

I'm trying to use the plugin to initiate a cloud scan in the following way: fortifyRemoteAnalysis remoteAnalysisProjectType: fortifyMaven(buildFile: ''), uploadSSC: [appName: 'my-app-name', appVersion: 'my-version']

The generated command looks the following: cloudscan -sscurl <my-ssc-url> -ssctoken start -bt mvn -upload -application my-app-name -version my-version -uptoken

It is missing the actual ssctoken and uptoken. The command fails to execute correctly without those tokens. The tokens are configured correctly on the Manage Jenkins page.

young-s-park commented 4 years ago

You need to enter a CloudCtrlToken in the "Controller token" field. For a CloudScan scan, this is the token that is used, not the "Authentication token" under the SSC URL field.

fabitamas commented 4 years ago

Thanks for the tip, the controller token field is filled out

Screen Shot 2020-04-29 at 4 57 59 PM
young-s-park commented 4 years ago

hmm...haven't seen or experienced this myself. Have you tried restarting Jenkins?

fabitamas commented 4 years ago

No, but I cannot really restart it... It is a main production jenkins instance of the company. It works on my test instance also.

fabitamas commented 4 years ago

Sorry, this was a mistake from the devops team, the controller token was actually not configured correctly.