Prerequisites for Configuring Cloudpath

Before you set up Cloudpath in your network, you need the following information:

Deploying the OVA (For Local Deployments)

  • VMware server or Microsoft Hyper-V Manager on which you’ll install the Cloudpath virtual appliance.
  • The URL where the image file resides
  • FQDN Hostname of the virtual appliance
  • IP address and subnet mask for the virtual appliance (not required if using DHCP)
  • Gateway IP address for your network (not required if using DHCP)
  • IP address of DNS server (not required if using DHCP)
  • A list of IP addresses that are allowed Administrative access (optional)
  • Service account security credentials

Setting up the Initial Account

  • Activation code issued from Cloudpath Licensing Server
  • HTTPS server certificate
  • Company Information (Domain, URL)
  • DNS hostname
  • Active Directory domain, DNS/IP address of AD server, and DN of AD domain or LDAP server
  • Web server certificate (public-signed)

If you are not using the Cloudpath onboard CA, you also need:

  • Public and Private key of existing CA
  • RADIUS server certificate (if not using onboard RADIUS server)

Configuring the Workflow

This section lists items to consider when you configure the workflow:

  • An idea about the types of access and policies you want to offer different users
  • Images and color schemes if you plan to customize the webpage display
  • AD group names for creating filters in the workflow
  • An idea about the security policy for passwords, vouchers, and certificates
    • Vouchers have configurable format and validity periods
    • Certificates have configurable key lengths, algorithm types, and validity periods
  • The SSID for the secure network
    • If using VLANS to apply policy, you should have the VLAN IDs
Note: For SSID configuration, see Configuring Cloudpath to Integrate With a Ruckus Wireless LAN Controller.
  • A list of conflicting SSIDs to prevent roaming (for example, open SSIDs)
  • An idea about which OS families and versions to support
  • Additional requirements for device configurations (for example, enable firewall, proxy, verify antivirus, enable screen lock pass code)