• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Component/s: netsparker-cloud-scan-plugin
• Labels:

  None

[JENKINS-66163] Netsparker Enterprise Plugin: Get scan info error ERROR: > Netsparker Enterprise Plugin: null

Pawandeep Singh created issue - 2021-07-16 19:24

Pawandeep Singh made changes - 2021-07-16 19:25

Description

Original: Upgrading to Netsparker plugin version 2.0.0 is giving error immediately after starting scan. > Netsparker Enterprise Plugin: Scan step created... > Netsparker Enterprise Plugin: Requesting scan... > Netsparker Enterprise Plugin: Response status code: 201 > Netsparker Enterprise Plugin: Scan requested successfully. > Netsparker Enterprise Plugin: Requesting scan info... > Netsparker Enterprise Plugin: Response scan info status code: 400 > Netsparker Enterprise Plugin: Get scan info error ERROR: > Netsparker Enterprise Plugin: null > Netsparker Enterprise Plugin: Requesting scan cancel... > Netsparker Enterprise Plugin: Response scan cancel status code: 200

New: After upgrading to Netsparker plugin version 2.0.0 , It starts giving error immediately after starting scan. > Netsparker Enterprise Plugin: Scan step created...  > Netsparker Enterprise Plugin: Requesting scan...  > Netsparker Enterprise Plugin: Response status code: 201  > Netsparker Enterprise Plugin: Scan requested successfully.  > Netsparker Enterprise Plugin: Requesting scan info...  > Netsparker Enterprise Plugin: Response scan info status code: 400  > Netsparker Enterprise Plugin: Get scan info error  ERROR: > Netsparker Enterprise Plugin: null  > Netsparker Enterprise Plugin: Requesting scan cancel...  > Netsparker Enterprise Plugin: Response scan cancel status code: 200

Collapse comment: Tri Effendi added a comment - 2021-07-23 11:18

Tri Effendi added a comment - 2021-07-23 11:18

i faced the similar issues, and asked the netsparker support. It turned out there are 3 additional mandatory parameters in v2 that must be stated in our Jenkins pipeline script:

• ncConfirmed
• ncIgnoreFalsePositive
• ncIgnoreRiskAccepted

My script goes like this and successfully running again:

step([$class: 'NCScanBuilder', ncApiToken: '$APITOKEN', ncScanType: 'FullWithPrimaryProfile', ncWebsiteId: 'ed9f0xxxxxxxxxxxf03f0b886', ncDoNotFail: true, ncConfirmed: false, ncIgnoreFalsePositive: false, ncIgnoreRiskAccepted: false])

 

Hope it helps.

Expand comment: Tri Effendi added a comment - 2021-07-23 11:18

Tri Effendi added a comment - 2021-07-23 11:18 i faced the similar issues, and asked the netsparker support. It turned out there are 3 additional mandatory parameters in v2 that must be stated in our Jenkins pipeline script: ncConfirmed ncIgnoreFalsePositive ncIgnoreRiskAccepted My script goes like this and successfully running again: step( [$class: 'NCScanBuilder', ncApiToken: '$APITOKEN', ncScanType: 'FullWithPrimaryProfile', ncWebsiteId: 'ed9f0xxxxxxxxxxxf03f0b886', ncDoNotFail: true, ncConfirmed: false, ncIgnoreFalsePositive: false, ncIgnoreRiskAccepted: false] )   Hope it helps.

Collapse comment: Pawandeep Singh added a comment - 2021-07-27 21:05

Pawandeep Singh added a comment - 2021-07-27 21:05

Thanks tsuriadi

I have added the additional parameters  and it started working.

ncDoNotFail: true, ncConfirmed: false, ncIgnoreFalsePositive: false, ncIgnoreRiskAccepted: false

Expand comment: Pawandeep Singh added a comment - 2021-07-27 21:05

Pawandeep Singh added a comment - 2021-07-27 21:05 Thanks tsuriadi I have added the additional parameters  and it started working. ncDoNotFail: true, ncConfirmed: false, ncIgnoreFalsePositive: false, ncIgnoreRiskAccepted: false

Pawandeep Singh made changes - 2021-07-27 21:06

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]