eCDN Integration Cheat Sheet

Customer integration requirements

eCDN Vendor activation

• Different for each vendor
  1) Kollective requires portal integration activation with token creation
  2) Hive requires customer ID communication and application association

Browser policy deployment

• This is an Edge or Chrome browser policy that needs to be deployed by the customer
• The purpose is internal IP exposure for specific hostnames (brandlive.com, onlinexperiences.com)
• Internal IPs are used for grouping, reporting and peering behavior management
• Specific vendor and browser policies for windows and mac are attached to this article
  Be sure to send the appropriate files to the customer

Network locations

• These are groupings of customer computers (typically by internal IP)
• The purpose of these groupings is two-fold
  1) Improve reporting accuracy
  2) Enable specific behavior modifications
• Kollective calls these localities
• Hive calls these siteinfo
• Kollective's group management is self-serviceable, highly configurable and flexible
• Hive's group management is less sophisticated, requires Hive activation and has limitations

Peer to Peer traffic enablement

• This isn't always needed but is required when there's a locked down environment
• Enables peer to peer communication using WebRTC/UDP when blocked
• Typically needed in Windows Defender or other security clients like ZScaler

Brandlive integration requirements

Super Admin enablement

• Kollective
  
  
• Hive
  
   

Channel Enablement and Configuration

Once enabled in Super Admin, navigate to the integrations menu and click "Add" to be prompted to choose the new integration you would like to add.

• Kollective
  
  Tenant ID and Service Token from Kollective Portal
  
   
• Hive
  
  Customer ID required - obtained from Hive
  
   

Browser Policies: