Home > Wireless LAN > MR Splash Page > Configuring Splash Page Authentication with an LDAP Server

Configuring Splash Page Authentication with an LDAP Server

Table of contents
No headers

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 Dashboard to use your LDAP server for user authentication:

  1. Log into Dashboard.
  2. Navigate to Configure > Access control.
  3. Set the Association requirement to Open


  1. Set the Network sign-on method to Sign-on Splash page and from the Authentication server drop down select Use my LDAP server.

  1. Click Add a server for LDAP servers.
  2. Enter the IP address of your LDAP server in the Host field and the LDAP listening port which is normally 389 in the Port field.
  3. For LDAP admin, enter the distinguished name of the administrative account to be used by the AP to bind to your LDAP server, for example cn=admin,dc=example,dc=com, and the password.


  1. Click the Save Changes button

This completes the configuration that is necessary in Dashboard. Further configuration will need to be addressed either at the LDAP server or at the client

Note: Client credentials will be passed along to the server by the access point. As such, ensure that firewall rules are in place to allow communication from your access points to the LDAP server(s) IP and port.

When using splash page authentication, captive portal strength settings take precedence over configured traffic shaping and firewall rules. This means traffic shaping and firewall rules will only apply after Splash page authentication has occurred successfully. If firewall or traffic shaping rules are configured on an SSID, use the "Block all access until sign-on is complete" captive portal strength setting to apply the principle of least privilege to the SSID. This captive portal strength will ensure all traffic is blocked until the desired firewall and traffic shaping rules can be applied.

Last modified



This page has no classifications.

Explore the Product

Click to Learn More

Article ID

ID: 1956

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community