|Applies To||RSA Product Set: SecurID Access|
|Issue||Connectivity between the identity router (IDR) and its SecurID Access cloud tenant is being questioned.|
|Resolution||A helpful troubleshooting step is to try accessing the Secure Connector health.API URL either from a browser on the same subnet as the IDR proxy interface or directly from the IDR using the wget command.|
The URL is of the form <tenant id>.auth.securid.com/secure-connector-fe/health.api where <tenant id> is the value initially set in the Administrator Console under My Account > Company Settings > Company Information tab > Company ID field.
The following is an example wget command from the IDR command line. The --bind-address switch should specify the IDR's proxy IP address. Connection OK is returned when successful.
See Access SSH for Identity Router Troubleshooting to access the IDR command line:
[email@example.com ~]$ wget --no-check-certificate --bind-address <IDR Proxy IP> https://mycompany.auth.securid.com/secure-connector-fe/health.api
--2019-01-09 21:58:28-- https://mycompany.auth.securid.com/secure-connector-fe/health.api
Resolving mycompany.auth.securid.com... 22.214.171.124
Connecting to mycompany.auth.securid.com|126.96.36.199|:443... connected.
HTTP request sent, awaiting response... 200
Length: 13 [text/plain]
Saving to: `health.api.1'
100%[==========================================================>] 13 --.-K/s in 0s
2019-01-09 21:58:30 (2.70 MB/s) - `health.api.1' saved [13/13]
[firstname.lastname@example.org ~]$ more health.api