Most of Meraki's customers who need a captive portal (UAM) authentication system on their wireless networks use the customizable splash pages that are hosted by Meraki's cloud and configured in Meraki Dashboard. However, some network administrators may prefer to host a captive portal page on their own servers, a feature we refer to as EXCAP.
The Cisco Meraki MR Access Points and MX Security Appliance allow a Splash Page to be configured, requiring users to interact with this captive portal before being granted network access. One configuration option for this Splash Page is to allow authentication with an existing RADIUS server on the network, so users must enter their domain credentials to get through the Splash Page. This article outlines the Dashboard and RADIUS configuration steps to use a RADIUS server with a sign-on Splash Pag
A splash page (also known as a 'captive portal') can provide a branded experience to wireless users, in addition to prompting for username/password credentials. For example, the splash page can display a corporate logo and color scheme. The splash page can also show the terms of service, which might include an acceptable use agreement or a privacy statement. This can be useful for an open guest wireless network.
The Cisco Meraki MR access points and MX security appliance allow administrators to set up a splash page, which can be further configured to link up with a Facebook page, so a user is required to "like" that page before they can join the network. This article outlines some additional requirements and considerations when using Facebook Wi-Fi.
Using a Sign-on Splash Page with Meraki Authentication is a convenient way to control user access without an Active Directory or RADIUS server. Self-registration allows users to create their own accounts for these SSIDs, without requiring an administrator manually enter this information. This article outlines how to configure self-registration, as well as describe the end-user experience.
A splash page provides a customized branding experience to wireless users and prompts for username/password credentials. Billing SSIDs used for hotspots utilize splash pages to obtain payment information prior to granting access to the internet. Splash page frequency varies depending on the SSID configuration and the certain variables that control the splash behavior.
In some cases, a configured splash page may appear more or less frequently than intended on client devices, or not at all. This article describes what occurs when a user passes through a Splash page, the possible reasons why a Splash page is appearing at a frequency that is different than what is configured on the Dashboard, and how to resolve these problems.
The Meraki sign-on Splash Page can be integrated with Google OAuth, requiring users to log in with credentials from a custom Google domain for network access. This Splash Page can be configured to block Internet access until sign-on is complete, but certain domains need to be added to the "walled garden" of allowed websites in order for OAuth to complete. This article outlines how to allow Google OAuth to operate while still limiting pre-authentication Internet access.