09 Aug 2024 01:41 PM
Hi Gurus,
Is it possible to use an ActiveGate instead of the environment URL for configuring communication settings?
I understand that this is available through oneagentctl.
Thank you!
09 Aug 2024 01:57 PM
Hello Hamdy,
You can try to add the EAG URL in additional addresses, once the connection fails with the cluster URL, it will go for the EAG url.
Thanks,
Islam
09 Aug 2024 02:09 PM - edited 09 Aug 2024 02:16 PM
Thank you, @islam_zidan .
Have you tested this solution, and did it work as expected? As you know, asking clients to add the tenant URL can be problematic, especially if firewall restrictions prevent direct server access to the SaaS tenant. In such cases, the traffic might route through the EAG URL.
If this method has been tested successfully and operates smoothly in the background without causing UI errors, we can proceed with it.
Best Regards,
Mohamed
09 Aug 2024 08:30 PM
we leveraged a DNS alias that house 4 AG's that then allowed the proxy and handling of not just the installer download but also the communication routes.
09 Aug 2024 08:34 PM
This might be a shot in the dark but you can try: https://{{active gate url}}:{{Port}/e/{{TENANT ID}}
11 Aug 2024 11:18 AM
Hi @ChadTurner , Thank you for your input. Unfortunately, the environment ID is the only accepted value for the main communication field. While it may be possible to include it in additional communication fields, it cannot be used in the primary communication address.
I think I will go with oneagentctl directly, as I have tested that and it will fail if the main connection is not reachable