What you'll need
- Admin access to your Meraki Dashboard (Organization-level, to enable API access)
- The Meraki Dashboard API enabled for your organization
- Your target SSID configured as Open (no encryption)
- If using credential-based (Sign-On) login: a RADIUS server that's reachable from the public internet — Meraki cloud sends RADIUS requests from Meraki's own servers, not from the access point
Steps
- In the Meraki Dashboard, go to Organization > Settings and turn on Dashboard API access. This is off by default and must be enabled before MyWiFi can talk to your network.
- Go to your admin Profile > API access and generate an API key. You'll enter this in MyWiFi in a later step — keep it somewhere safe in the meantime.
- Go to Wireless > Configure > Access control for your guest SSID. Set Security to Open (no encryption).
- Under Splash page, choose Click-through for a simple "tap to agree" flow, or Sign-on with my RADIUS server if you want guests to log in with credentials. Leave the Custom Splash URL field for now — MyWiFi sets this automatically once connected.
- Still under Access control, turn on Walled Garden and add MyWiFi's server domain/IP so guest devices can load the splash page before they're authenticated. Without this, the splash page will never load.
- If you chose Sign-On mode, also add a RADIUS server entry under Wireless > Configure > Access control > RADIUS servers pointing to MyWiFi's RADIUS server, and make sure that server has a public IP — Meraki's cloud, not your access point, is what sends the RADIUS requests.
- In the MyWiFi dashboard, go to Devices and click Add Device.
- Select the Location, name the device, and under Select Your Hardware choose Cisco Meraki.
- Enter your Meraki connection details as prompted — typically your API key plus the Organization and Network you want to connect — and save. MyWiFi will push the splash page URL to Meraki automatically from here.
Best practice: Meraki's Dashboard API is rate-limited to roughly 5 calls per second per organization, so if you're rolling this out across many sites at once, stagger the setup rather than adding every location back-to-back.
Comments
Please sign in to leave a comment.