What firewall or network configurations are required for the Desktop Application?

📘 Introduction

For the GeoCloud Drive Desktop Application to function correctly and synchronise data, your network environment must allow specific traffic. If you are behind a corporate firewall or proxy, please ensure the following rules are configured to allow communication with our services.

🌍 Network Allowlist Rules

Domain / Endpoint	Port	Protocol	Direction	Purpose
`hxauth.com`	443	TCP	Outgoing	User Authentication (OpenID)
`hxdr.app`	443	TCP	Outgoing	API Communication (GraphQL)
`drive-desktop.geocloud.hexagon.com`	443	TCP	Outgoing	Software Auto-Updates
`telemetry.geocloud.hexagon.com`	443	TCP	Outgoing	Application Logs & Metrics
`*.launchdarkly.com`	443	TCP	Outgoing	Feature Flags & Real-time Updates
`localhost`	4200	TCP	Incoming	Local Desktop App Communication

Detailed Path Information

If your firewall requires specific paths rather than wildcards, please ensure these specific URLs are whitelisted:

Authentication: hxauth.com/auth/realms/geo-hxdr-prod/.well-known/openid-configuration
API Endpoint: hxdr.app/graphql
Auto-Update: drive-desktop.geocloud.hexagon.com
Monitoring: telemetry.geocloud.hexagon.com
Feature Flags (LaunchDarkly):
- clientstream.launchdarkly.com
- mobile.launchdarkly.com
- app.launchdarkly.com

Note: The application uses localhost:4200 for internal communication between app components. Blocking this port on the local machine may prevent the application from launching or logging in.