Documentation
  • Getting Started
  • WiFi Integration
    • Summary of supported WiFi vendors
      • Cisco Meraki
        • Meraki oAuth integration
      • Cisco Catalyst WLC (IOS-XE)
      • Cisco Meraki Easy PSK
      • Aruba - Unbound MPSK
      • Fortinet (FortiGate Secure Wireless Controller)
      • Extreme Networks
      • Ruckus SmartZone
      • Cambium cnMaestro
      • Juniper (Mist)
      • TP-Link Omada
      • Huawei - iMaster NCE-Campus
  • Service management
    • Dashboard
    • Managing Accounts
    • Groups
    • Managing Networks
      • Network Managers
    • Units
    • General options
      • Personal Area Networks (PAN)
      • Service Options
      • Organization details
    • Network Policies
    • WiFi Portal & Onboarding
      • Access Control options
      • WiFi Portal options
      • IoT Devices Authentication
      • WiFi Portal distribution
    • Visitors (beta)
    • Admins
      • Multi Organizations
    • Account settings
    • My Profile
    • Support platforms integrations
    • Service Monitoring and Assurance
      • Anomalies
      • Activity Logs
      • Network Health
  • Cloud Identity Platforms integrations
    • Coworking management platforms
      • Optix
      • Office RnD
      • Nexudus
      • Andcards
    • Property Management Systems
      • Oracle Opera Cloud
      • Mews
      • Cloudbeds
      • Apaleo
    • Enterprise cloud IdPs
      • Microsoft Entra ID (SAML)
      • Microsoft Entra ID (oAuth)
      • Google Workspace (oAuth)
      • Shibboleth
      • Group mapping
    • Passwordless SSO
      • Custom HTTP Request
  • MSP Operations
    • MSP Dashboard
    • MSP Account settings
  • Add-ons
    • Billing
    • White label
    • Passpoint
    • SMS Services - via Twilio
  • APIs
    • Getting Started
    • Account management
  • PRODUCT
    • Coming soon...
      • Engenius Cloud
      • Zyxel Nebula (Pro)
    • Changelog
    • Datasheet
  • Solution guides
    • Student living
      • Sample FAQ: WiFi for the Resident Hall
    • BYOD
Powered by GitBook
On this page
  • Omada setup
  • Cusna setup (Controller mode)
  • Cusna setup (Cloud mode)
  • Cusna setup (Open APIs mode)
  • Operating Cusna
  • Creating Networks
  • Creating Accounts

Was this helpful?

  1. WiFi Integration
  2. Summary of supported WiFi vendors

TP-Link Omada

PreviousJuniper (Mist)NextHuawei - iMaster NCE-Campus

Last updated 6 months ago

Was this helpful?

Omada setup

For each Network you need to setup a Site in your Omada account.

Once you have the Site, create a WLAN network and an SSID.

Go to Settings > Wireless Networks and click + Create New Wireless Network. And the Network Name (SSID), for example "Residents WiFi".

Select PPSK without RADIUS in the Security dropdown.

On the PPSK Profile, you need to add create and assign at least one PPSK user in order to create the SSID. Click on the menu and select the last item, Create new PPSK Profile.

The Create New PPSK Profile dialog opens. Enter a Name, such as "Default". in the PPSK1 section, enter as Name something like "Default PPSK" and in the Passphrase input enter a long, difficult to guess Passphrase.

Once you have create your default PPSK Profile, you'' return to the main screen, and select the profile just created in the dropdown PPSK Profile.

Click Apply to save.

Cusna implements an automatic VLAN management to segregate each resident traffic. Cusna uses the slot of VLANs 2000-4000 so you should avoid using these VLANs for any other purposes.

Cusna setup (Controller mode)

Get the account hostname

To connect Cusna to your Omada instance account you need to get the hostname of your instance. You can easily identify the hostname form the URL base of your browser once you are logged in in your Omada account.

In the screenshot above the hostname would be: omada.cusna.io:8043. Do not enter https. Make sure to enter the port if you see it in your URL.

If your controller has a self-signed SSL certificate, APIs return an error, so the integration won't work.

Oamda uses the user credentials to generate the tokens required to authenticate the APIS. We suggest creating a dedicated API User to connect to Cusna.

Go to Admin and click +Add New Admin Account. Select Cloud User as Administrator Type and All as Site Privileges.

Link Omada to Cusna

Log in your Cusna account and go to Settings. In the WiFi integration section, select TP-Link.

Enter the requested inputs:

  • Omada tenant hostname: the hostname of your Omada instance

  • Username: username of the Omada admin user

  • Password: username of the Omada admin user

Cusna setup (Cloud mode)

Get the account hostname

To connect Cusna to your Omada instance account you need to get the hostname of your instance. You can easily identify the hostname form the URL base of your browser once you are logged in in your Omada account.

With reference to the screenshot above

  1. take the hostname part: "use1-omada-controller.tplinkcloud.com"

  2. transform it as follow adding the "api" string: "use1-api-omada-controller.tplinkcloud.com"

  3. Copy the OmandacId value, which is the string right after the first "/": "5492cc657ffb80e24e8afe386f8ed4bb"

Oamda uses the user credentials to generate the tokens required to authenticate the APIS. We suggest creating a dedicated API User to connect to Cusna.

Go to Admin and click +Add New Admin Account. Select Local User as Administrator Type and All as Site Privileges.

Link Omada to Cusna

Log in your Cusna account and go to Settings. In the WiFi integration section, select TP-Link.

Enter the requested inputs:

  • Omada tenant hostname: the hostname of your Omada account as indicated above

  • OmandacId: the id of your account as indicated above

  • Username: username of the Omada admin user

  • Password: username of the Omada admin user

Cusna setup (Open APIs mode)

Setup an API Client

In Global View or MSP View, go to Settings > Platform Integration > Open API. 2. Click + Add New App. The Open API dialog appears.

Enter a name in the App Name, select the following options:

  • Mode: Client

  • Role: Administrator

  • Site Privileges: All

Click Apply.

From the main page, copy the Client ID and Client Secret.

Click on the eye icon, to open the View Open API Attributes and copy the Interface Access Address and the Omada ID.

Link Omada to Cusna

Log in your Cusna account and go to Settings. In the WiFi integration section, select TP-Link and select Open API in the Controller Mode.

Enter the requested inputs:

  • Interface Access Address:

  • Omada ID:

  • Client ID:

  • Client Secret:

Operating Cusna

Creating Networks

When you create or edit a Network in the Cusna dashboard, in the WiFi configuration section, you have to pick the Site, WLAN and SSID to associate to the property.

Creating Accounts

When you create a new Account, a new PSK user will be created in your Omada account with a predefined WiFi Passphrase. The user receives an activation email with the default passphrase and QR code, and a link to the WiFi Portal where he can change the passphrase.

To avoid synchronization problems, do not manage manually the PPSKs in the Omada interface