When using Apple Open Directory you must specify the BindDN for the LDAP admin setting. This BindDN must be the Distinguished Name of the Open Directory administrator that binds to the Open Directory server.
Cisco Meraki Billing allows you to charge users for network access. It is designed to be easy to use and can be setup in just a few minutes. To use this function, start by choosing Billing (paid access) under Configure > Access control > Network access > Splash page.
Prepaid cards enable a network owner to generate pin codes and provide those pin codes to potential users. The network owner can use this as a way to charge users for access without using the Cisco Meraki payment system.
Cisco Meraki access points support authentication through an externally hosted LDAP server. After the server is configured, the dashboard will require a minimal amount of setup to allow for LDAP authentication. Please use the steps below to successfully configure the Dashboard to use your LDAP server for user authentication:
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.
By default a Billing Splash page cannot be customized. However, Billing Splash pages using Prepaid cards can be customized when Fast prepaid login is enabled. This article will outline how to enable and configure the Fast Prepaid Card billing option.
When the Meraki click-through splash-page is enabled, users must view and acknowledge the splash page before being allowed on the network. The following instructions explain how to enable and configure an SSID with a click-through splash page:
Cisco Meraki devices (MR access points and MX security appliances) support the use of a sign-on Splash Page, requiring network users to authenticate in a web browser before being allowed access to the network. This splash page can be integrated with an Active Directory server, allowing users to provide their domain credentials to gain access. This article outlines how to configure a sign-on Splash Page with Active Directory
Dashboard provides the ability to host a sign-on splash page that can use one or more external RADIUS servers for authenticating users. This document describes the details of how and when those RADIUS servers will be contacted for authentication, and how the Dashboard will behave if it is unable to contact any of the configured servers. This does not apply to network association using WPA2-Enterprise with 802.1x authentication.
By default, when using Active Directory for Splash Page authentication, all users in AD can be granted access. However, by using OUs and a custom AD admin account, it is possible to limit which users can get through authentication. This document will show you how to limit the scope of users that can be authenticated to an SSID using a Splash Page with Active Directory Integration.
This article details functionality and traffic flow for different types of splash pages, which may be helpful for reference or troubleshooting purposes.
Sign-on Splash page with Active Directory authentication uses LDAP/TLS to securely bind to a Global Catalog for authentication. Specifically, the AP performs a secure LDAP bind to the Domain controller on Global Catalog TCP port 3268 using the admin credentials specified in Dashboard and searches the directory for the user with the credentials entered into the splash page.
MAC-based authentication restricts wireless access to specific client devices but traditionally requires a RADIUS server. For smaller deployments, it is easier to configure MAC-based authentication using a Sign-on Splash Page.
No articles with the article type topic could be found.
