Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

CONNECT EAP

CONNECT URL and certificate requirements

  • Last UpdatedJan 30, 2026
  • 2 minute read

This document details the requirements for connecting to CONNECT, including allowed URLs, domain rules, and certificate validation.

Domain rules

CONNECT enforces strict domain validation. CONNECT supports both wildcard and explicit domain configurations. Additional CONNECT applications may use subdomains under *.connect.aveva.com. Wildcard domain configuration is recommended to ensure easier configuration and more flexible coverage. Explicit domains offer more granular control.

  • Wildcard domains (recommended): If a domain is listed with a wildcard (like *.connect.aveva.com), all subdomains are permitted.

  • Explicit domains: Only listed domains are permitted; wildcards are not allowed unless explicitly stated.

  • Domain matching: All connections must match the listed domains exactly or conform to the specified wildcard pattern.

Allowed URLs

If your organization uses a proxy server or firewall configured with least-privileged access, specific domains must be allowed to enable successful authentication and access to CONNECT services.

does not provide IP addresses for allow listing. Instead, we recommend using DNS-based firewall rules to manage domain-level access. This approach ensures flexibility and compatibility with certificate validation and dynamic service endpoints.

The following URLs must be accessible for CONNECT and its features to function correctly.

Category

URL/Endpoint

Global endpoint

  • online.wonderware.com

Product: Insight

  • int.online.wonderware.com

  • stats.g.doubleclick.net

  • login.microsoftonline.com

  • fonts.gstatic.com

  • connect.aveva.com

  • cdn.connect.aveva.com

  • identity.connect.aveva.com

  • insight.connect.aveva.com

  • license.connect.aveva.com

  • profile.connect.aveva.com

  • signin.connect.aveva.com

  • msecnd.net

  • crl.verisign.com

  • crl.thawte.com

  • crl.pki.goog

  • crl.digicert.com

  • crl3.digicert.com

  • crl4.digicert.com

  • crl.identrust.com

  • ocsp.digicert.com

  • isrg.trustid.ocsp.identrust.com

  • msocsp.com

  • amazontrust.com

  • tiles.virtualearth.net

  • secure.aadcdn.microsoftonline-p.com

  • msftauth.net

  • login.microsoft.net

  • fonts.googleapis.com

  • insightcdn3.azureedge.net

  • events.launchdarkly.com

  • app.launchdarkly.com

  • data.eu.pendo.io

  • pendo-eu-static.storage.googleapis.com

  • cdn.eu.pendo.io

  • pendo-eu-static-5632378061062144.storage.googleapis.com

  • login.windows.net

  • sso.aveva.com

  • aadcdn.msftauth.net

  • ajax.googleapis.com

  • api.connect.aveva.com

  • portal.services.connect.aveva.com

  • services.connect.aveva.com

  • services2.connect.aveva.com

  • integrationstudio.connect.aveva.com

  • storage.services.connect.aveva.com

  • storage-secondary.connect.aveva.com

  • www.google-analytics.com

Feature: Insight browsing

  • ttappusw.insight.connect.aveva.com

  • tthelp.us-insight.connect.aveva.com

  • static.intercomassets.com

  • downloads.intercomcdn.com

  • widget.intercom.io

    • North America

      • portal.us-insight.connect.aveva.com

      • cdn.us-insight.connect.aveva.com

    • Europe

      • online.wonderware.eu

      • portal.eu-insight.connect.aveva.com

      • cdn.eu-insight.connect.aveva.com

      • ttappeun.insight.connect.aveva.com

    • Australia

      • online.wonderware.net.au

      • portal.au-insight.connect.aveva.com

      • cdn.au-insight.connect.aveva.com

      • ttappaue.insight.connect.aveva.com

Feature: Insight publishing

  • online.wonderware.com

    • North America

      • nch.online.wonderware.com

    • Europe

      • nch.online.wonderware.eu

    • Australia

      • nch-au.online.wonderware.com

Certificate requirements

CONNECT services rely on certificates issued by trusted authorities to secure communications. Your network must allow access to certificate validation endpoints to avoid authentication failures or service disruptions.

Each domain within CONNECT may use certificates from different issuers. Below is a breakdown of certificate usage and the corresponding validation URLs.

Issuer

Used by

Validation URLs

Let's Encrypt

(Authority X3)

  • signin.connect.aveva.com

  • OCSP

    http://ocsp.int-x3.letsencrypt.org

  • CRT

    http://cert.int-x3.letsencrypt.org/

  • OCSP/CRLS

    *.lencr.org

Amazon

  • identity.connect.aveva.com

  • connect.aveva.com

  • api.connect.aveva.com

  • CRL

    http://crl.r2m03.amazontrust.com

  • OCSP

    http://ocsp.r2m03.amazontrust.com

  • CRT

    http://crt.r2m03.amazontrust.com

DigiCert

(SHA2 secure server CA)

  • profile.connect.aveva.com

  • services.connect.aveva.com

  • services2.connect.aveva.com

  • storage.services.connect.aveva.com

  • storage-secondary.services.connect.aveva.com

  • CRL

    http://crl3.digicert.com

  • OCSP

    http://ocsp.digicert.com