Troubleshooting GRC integrations

This section helps you remedy common problems and understand how better to use the Archer API for GRC integrations.

Issue	Solution
Invalid IP address range.	Ensure that you are attempting to connect from an IP address that is allowed by the IP address restrictions for the login you are using. Ensure you have added the required domains for your Veracode account to the allowlist for your organization. Refer to the complete list of domains and IP addresses to add to your allowlist.
Invalid login type.	Ensure that you are providing credentials for an API class login with the Archer API role.
Invalid or null token.	Each login account is limited to using five tokens at a time to download Archer reports. The last five generated tokens are valid. All tokens expire after 30 days whether they are used or not. Using invalid tokens returns HTTP status code 403.
Incorrect date format.	Ensure the date format for the date_from and date_to fields is dd-mm-yyyy.
The report is not ready.	If you try to call downloadarcherreport.do before generatearcherreport.do has completed, you receive HTTP status code 204 to indicate no content is available. Try to download the report at a later time. After an excessively long time, if the Veracode Platform does not return the report, contact Veracode Technical Support.
The results file is too large.	When attempting to fetch the Archer feed for a large number of applications at the same time, the Veracode Platform may return HTTP status code 500. Veracode recommends that you fetch the data using the optional arguments for the Archer API to limit the scope of the data being pulled, for example using scan_type or a date range. After all the historical data is in place, use one of these period arguments to pull data on a scheduled basis: yesterday, last_week, or last_month. Alternatively, you can use the asynchronous calls generatearcherreport.do and downloadarcherreport.do.