I see in the documentation that a MR33 wireless AP can use AD authentication and a "splash-page" sign on option.
Does this require that a certificate be installed on the Meraki AP? One that is valid on a public / commercial level, so that it doesn't throw up errors when users see it? Or is that not an issue?
Solved! Go to solution.
The web page comes from the cloud and should not throw a certificate error The certificate you install on your AD is to validate itself against the AP, when doing logins, not for serving web pages.
By AD Authentication do you mean 802.1x Radius? If so then it does look like you could have that selected for Network Access section and the spash 'Click-Through' is served by the Meraki servers so no certificate needed.
Actually, I was think of this
unless that requires the MX appliance
You can do this in a few different ways. You can do 802.1x which can be implemented using AD.
Or, you can use splash page sign on with AD authentication. You will need to have a certificate on your server so the AP can validate against it when logging users on. The certificate can be self-signed but it is not recommended.
The AD server will have a certificate (self-signed), but I was wondering about the page that actually gets served up to the wireless clients.
That comes from the Meraki AP correct? I just wanted to make sure they didn't get certificate warnings/errors from it
The web page comes from the cloud and should not throw a certificate error The certificate you install on your AD is to validate itself against the AP, when doing logins, not for serving web pages.