Use this article when a guest or an employee signs in with SSO, or submits the portal form, but the connection is not completed on a Cisco Meraki network. For example, the identity provider (IdP) confirms the sign-in, and the portal then shows an error or no Internet access is granted.
Prerequisites
Before starting, ensure that you have the following prerequisites:
- Access to Cloudi-Fi's admin console
- Access to the Cisco Meraki dashboard
- A test account for the IdP, and a test device connected to the affected guest SSID
1. Identify the Meraki setup
The checks depend on the way the SSID is configured in Meraki. Go to "Wireless" > "Configure" > "Access Control", select the SSID, and read the splash page and RADIUS settings.
- Click-through with the API integration: see How to enable Cloudi-Fi with Cisco Meraki MX/MR (API). Follow steps 2, 3, and 5.
- MR with RADIUS: see How to enable Cloudi-Fi with Cisco Meraki MR with Radius. Follow steps 2 to 5.
2. Find where the sign-in stops
- In the Cloudi-Fi admin console, open "Locations". At the end of the line of the affected location, click the three-dot button and select "Try portal". Sign in with the test account.
- Repeat the sign-in on the test device, connected to the guest SSID.
Compare both results:
- "Try portal" fails too. The issue is in the SAML configuration or in the IdP, not in Meraki. Check the setup article for your IdP, listed in How to authenticate your employee/partner with SAML method, then contact the IdP administrator for an error shown by the IdP itself.
- "Try portal" works, but the test on the device fails. Continue with step 3.
3. Check the walled garden for the IdP
Before sign-in, guests must reach the domains of the IdP. A missing domain stops the flow after the IdP page.
- In the Meraki dashboard, go to "Wireless" > "Configure" > "Access Control" (or "Security & SD-WAN" > "Configure" > "Access Control" for MX), and select the SSID.
- Compare the walled garden ranges with the domains of your IdP in Set up a Walled Garden for your captive portal.
- Generate a HAR file during a failing sign-in and find the last request that succeeded: the IdP, the return to Cloudi-Fi, or the access grant from Meraki. See How to generate a HAR file.
The success of the IdP alone does not prove that the Wi-Fi connection succeeded. The return to Cloudi-Fi and the access grant from Meraki are separate steps.
4. Test RADIUS (MR with RADIUS only)
- In the Meraki dashboard, open the RADIUS settings of the SSID, and click the "Test" link next to the RADIUS server.
- Enter a valid test account, and run the test.
Read the result:
- Timeout. Meraki does not reach the RADIUS server. Check the server IP address and ports (UDP 1812 and 1813) in Radius and Syslog Servers for Guest captive portal, and the firewall rules between Meraki and the Cloudi-Fi servers.
- Rejected. The server answers, but refuses the request. Check the shared secret in Meraki. Ask Cloudi-Fi support to confirm it.
- Accepted. RADIUS works. Go to step 5.
5. Check the client authorization in Meraki
- Complete a sign-in on the test device.
- In the Meraki dashboard, find the client in "Network-wide" > "Monitor" > "Clients", and check whether it is authorized.
- The client is not authorized after a successful sign-in. Collect the Meraki event log for the time of the test, and the HAR file, then contact support.
- The client is authorized, but has no Internet access. See Guest devices get an IP address but DNS or Internet access is blocked on Cisco Meraki.
Use a device without a VPN or security agent for the test. A computer with an active agent behaves differently from a phone without one, so the results are not comparable.
Contact your support
If the issue remains, contact the Cloudi-Fi support team and share the following information:
- The name of the location and of the SSID, and the Meraki setup (click-through or RADIUS)
- The Meraki Network name
- The name or MAC address of the access point used
- The date and time of the test, with the time zone
- The device model and operating system
- The device Mac Address and IP address
- The authorization status of the device in the Meraki dashboard
- The IdP in use and the result of "Try portal"
- The exact error message, with a screenshot
- A HAR file of the failing connection: web browser, Android, or Apple iPhone and iPad
- The result of the Meraki RADIUS test, if applicable
Never share passwords or the RADIUS secret.