NVD integration failing consistently

[superhumanben]

Since rolling out VR late last year we've never seen a fully clean pull from NVD. Recently with the change from API 1.0 to 2.0, we have not been able to pull anything at all. The initial errors are either NVD:0 or 404 errors. We're at a supported application version, we've signed up and implemented an API key, still having errors. Any thoughts on how to troubleshoot this issue further?

[Scott Flynn]

Sent you a message.  Please tell me your results.

[Martin T Jensen]

Have you upgraded to the latest version of NVD? the latest is 1.4.2 and uses a new API from NVD

[superhumanben]

Yeah, that's the version we're on. Sadly, we were having some issues before switching to 1.4.2 but have had zero successful pulls since we switched in December. At this point I think I just need to open a support ticket.

[Aaron Molenaar]

We upgraded to 1.4.2 in December and had sporadic issues. It took 4 attempts for me to get a successful API key and get all environments successfully connecting.

Unfortunately now, we are getting an error "Encountered error running the integration. Error: The payload attachment size is 176139155 bytes. It cannot exceed 100000000 bytes. Modify the integration instance parameters to ensure that the payload attachment size is within the specified limit."

It seems the throttling mentioned previously keep the payload size down and now nearly all imports are failing with above error (payload size varies). I have not yet found information on where the integration instance parameters are to adjust. Any quick reference would be appreciated.

Thanks.

[Nitesh Tolani]

This is controlled through the system property 'sn_sec_cmn.max_integration_payload_size'. Please feel free to update this property as per your requirements.