Failed couldn't Initialize

Found Version

Skyhigh Content Security Reporter 2.x

Description

Content Security Reporter can't retrieve logs from WebSaaS, even though when you test the connection, it reports as Successful.

In the Job Queue, you see the following error:

Failed - couldn't initialize 

How to Fix

To resolve this issue, increase the connection timeout and decrease the batch size interval:

1. On your CSR server, navigate to ...\Content Security Reporter\reporter\conf.
2. Add \resources\system to the \conf folder. For example:

...\Content Security Reporter\reporter\conf\resources\system.

3. Navigate to: ...\Content Security Reporter\reporter\conf\examples\resources\system
4. Copy the server.properties file you see to ...\Content Security Reporter\reporter\conf\resources\system.
5. Open .....\conf\resources\system\server.properties, in a file editor of your choice.
6. Locate the following block:

# Override the batch size for SaaS data.
# Value is in minutes and must be between 5 and 60.
# SaasDataBatchSize 60

# Override the Http timeout for retrieving SaaS data.
# Value is in minutes and must be between 1 and 60.
# SaasHttpTimeout 1

7. Remove the # before SaasDataBatchSize and SaasHttpTimeout.
8. Modify the values of both these entries to 20.

For example:

# Override the batch size for SaaS data.
# Value is in minutes and must be between 5 and 60.
SaasDataBatchSize 20
 

# Override the Http timeout for retrieving SaaS data.
# Value is in minutes and must be between 1 and 60.
SaasHttpTimeout 20

When you set these values to 20, data is retrieved in 20-minute batches with a 20-minute wait before timing out.

9. Save your changes.
10. Restart the CSR server and verify that the logs are being fetched from WebSaaS.