Desktop Connect requires outbound HTTPS connectivity to Prodoscore servers. Configure your firewall and network policies to allow the necessary domains and IPs.
Finding Your Base Domain
Your Prodoscore workspace URL tells you your base domain:
- Example URL:
https://acme.ag.prodoscore.com - Base domain: "acme" (the text before .ag.prodoscore.com)
Use your base domain in the whitelisting rules below.
Recommended: Wildcard Domain Whitelisting
This is the simplest and most recommended approach. Whitelist a single wildcard domain that covers all Prodoscore subdomains:
This single entry allows all necessary Prodoscore traffic without needing to specify individual subdomains.
Specific Subdomains (If Wildcard Not Permitted)
If your security policy does not allow wildcard domains, whitelist these specific subdomains instead:
api.ag.prodoscore.com— API and data uploadsauth.ag.prodoscore.com— Authentication and SSOportal.ag.prodoscore.com— Admin portal and UI[yourdomain].ag.prodoscore.com— Your specific workspace (e.g., acme.ag.prodoscore.com)
Additional Required Domains
The following additional domains are required for licensing and data storage:
origin.hrsaastech.com— License verificationstorage.googleapis.com— Data storage (Google Cloud Platform)
Port Requirements
HTTPS (Port 443): All traffic uses HTTPS on port 443. HTTP (port 80) is not used.
Firewall rule:
IP Whitelisting (Static IPs)
If your organization prefers IP-based whitelisting instead of domain whitelisting:
- Whitelist the static IPs of the licensing server and data storage infrastructure
- For Prodoscore portal (api.ag.prodoscore.com, auth.ag.prodoscore.com): allow outbound HTTPS to all IPs (Prodoscore uses a CDN with dynamic IPs)
Contact Prodoscore support at support@prodoscore.com to request the current static IP list for your region.
Web Security / SSL Inspection Tools
If your organization uses web security tools that inspect HTTPS traffic (Zscaler, Palo Alto Networks, Fortinet, etc.):
- Exclude Prodoscore domains from SSL/TLS inspection. Inspection breaks the client-server SSL handshake and blocks Desktop Connect.
- Exclude from authentication/login requirements. Do not require additional login credentials to access Prodoscore domains.
Example Zscaler configuration:
- Go to Policies > Firewall > Network Services
- Add *.ag.prodoscore.com to "Bypass List" (exclude from inspection)
- Ensure SSL inspection is disabled for this domain
Proxy Configuration
Direct Internet Access (Recommended): If computers have direct outbound HTTPS access to the internet, no proxy configuration is needed.
HTTP Proxy Required: If all outbound traffic must go through a proxy:
- Configure the proxy in Windows Settings (Proxy settings) or Mac System Settings (Network > Proxies)
- Ensure HTTPS traffic through the proxy is allowed on port 443
- Proxy should support CONNECT tunneling for HTTPS (most do)
Desktop Connect automatically detects and uses system proxy settings (no agent-level configuration needed).
Offline / Air-Gapped Environments
If computers have no internet access or very limited connectivity:
- Desktop Connect will collect data locally and queue it for upload
- When connectivity is restored (periodic sync to the internet), queued data is uploaded
- Portal visibility will show as "Offline" until data syncs
- For permanent offline environments, contact Prodoscore support for alternative data export solutions
VPN and Remote Access
Desktop Connect works through VPNs and remote access solutions (RDP, Citrix, TeamViewer, etc.). No special configuration needed — the agent just requires the same outbound HTTPS access as a regular internet connection.
Bandwidth Usage
Typical bandwidth consumption:
- ~5-20 MB per day per device (varies with activity volume)
- Uploads occur periodically (not continuously streaming)
- Data is compressed before upload
Low bandwidth usage — suitable even for offices with limited internet.
Compliance Checklist
✓ Whitelist domains: Have you added *.ag.prodoscore.com and related domains to your firewall allow list?
✓ SSL inspection: Have you excluded Prodoscore domains from SSL/TLS inspection tools?
✓ Antivirus exceptions: Have you added antivirus exceptions for the Desktop Connect processes?
✓ ✓ Test connectivity: After configuration, install Desktop Connect on a test machine and verify it can connect to Prodoscore and upload data.
For network troubleshooting, contact your IT/network team and include Prodoscore support: support@prodoscore.com.