Describe the bug
When trying to connect the Qualys VM CCF connector in Sentinel, we receive a 504 gateway timeout error.
To Reproduce
Steps to reproduce the behavior:
- Go to the Qualys VM data connector.
- Enter your credentials and choose any truncation limit - this value doesn't seem to change the behaviour of the connector.
- After about 5 minutes the connector will display a very generic 'cannot read properties of undefined (reading 'map')' error.
- Look at the activity log for the deployment and you will see the following error:
"subStatus": { "value": "GatewayTimeout", "localizedValue": "Gateway Timeout (HTTP Status Code: 504)" },
Expected behavior
The data connector should connect successfully.
Screenshots
Desktop (please complete the following information):
Windows 11. Issue occurs in all tested browsers; Edge, Firefox and Chrome.
Additional context
I have tried making an API call to the relevant Qualys VM endpoint as defined in the CCF definition and it can take up to 6 minutes before data is first returned. I suspect the timeout window of the CCF is much lower (some reading online suggests 3 minutes). This value can't be adjusted in the CCF polling definition, so the whole platform would need to be changed to support a longer timeout window.
Describe the bug
When trying to connect the Qualys VM CCF connector in Sentinel, we receive a 504 gateway timeout error.
To Reproduce
Steps to reproduce the behavior:
"subStatus": { "value": "GatewayTimeout", "localizedValue": "Gateway Timeout (HTTP Status Code: 504)" },Expected behavior
The data connector should connect successfully.
Screenshots
Desktop (please complete the following information):
Windows 11. Issue occurs in all tested browsers; Edge, Firefox and Chrome.
Additional context
I have tried making an API call to the relevant Qualys VM endpoint as defined in the CCF definition and it can take up to 6 minutes before data is first returned. I suspect the timeout window of the CCF is much lower (some reading online suggests 3 minutes). This value can't be adjusted in the CCF polling definition, so the whole platform would need to be changed to support a longer timeout window.