IIQ Cloud Gateway with Multi-Connector Adapter - Connection Test Failure

[jlgunnell (Jess Gunnell)]

Which IIQ version are you inquiring about?

8.4p1

Please share any images or screenshots, if relevant.

Share all details about your problem, including any error messages you may have received.

Our deployment leverages the IdentityIQ Cloud Gateway with several applications, including “Linux_Server”, which utilizes the multi-connector adapter. Exactly 20 minutes after running Test Connection it says "The connection to the Cloud Gateway was stopped.”

I can see from the Cloud Gateway logs that the connection test continues running, testing all 118 targets in the custom object. But we never get a definitive result in the IdentityIQ UI. Our aggregation tasks for the application are successful.

Is there a defined limitation with the Cloud Gateway (or other proxies) where the Test Connection will stop if a result is not available within 20 minutes?

[purovitzz (Hubert Pura)]

It’s not actually a Cloud Gateway limitation. The 20-minute cutoff usually comes from an HTTP timeout somewhere between your browser and IIQ — most often the reverse proxy, load balancer, or even Tomcat itself.

When you hit Test Connection, IIQ keeps that request open in the UI until it finishes. Meanwhile, the Cloud Gateway keeps testing all targets in the background (which you can see in the logs), but once the HTTP session hits the timeout (usually 1200 seconds), the connection gets closed and you see:

“The connection to the Cloud Gateway was stopped.”

Aggregation tasks work fine because they’re run asynchronously by the task scheduler, not through a long-running UI request.

Typical default timeouts: NGINX – proxy_read_timeout 1200s Apache – ProxyTimeout / Timeout F5/ALB – idle timeout ≈ 20 minutes Tomcat/Jetty – connectionTimeout or asyncTimeout

To fix it, you can:

Increase the timeout on your proxy/LB/app server (e.g., 3600s).

Reduce the per-target connect/read timeout in the connector.

Test smaller batches instead of all 118 targets at once.

Or move the connectivity test into a background task instead of running it directly from the UI.