Authentication Splash Screen Annoyance

[AGomez]

Hi there,

I have this annoyance with the Meraki User Authentication Splash screen. Now, it doesn't hinder work in the slightest, and the actual security portion is working exactly as intended. However, when a user goes to authenticate, they get an error saying that either their username or password is incorrect. But they will be granted access to the internet, the authentication check succeeds but there is no way of knowing unless you go back to, for example, Google and search for cat videos to check if you can get info flowing in/out.

For some extra context, we have our Meraki set up to utilize our Active Directory to authenticate users, which very well may be causing this annoyance. To top it off, we're currently (not for long) running on Windows Server 2008 R2, which is constantly causing challenges for me in this network environment. 

As I stated before, this is really no big deal. Everything works correctly and is secured the way we want. It's just annoying. 

Any thoughts would be greatly appreciated!

Thanks all,

AGomez

[ww]

What is the

"Captive portal strength " set to?

Block all access or allow non http?

[AGomez]

That's one of my issues figuring this out, I've looked at every settings page on the darn thing and can't find any advanced settings for the portal. Add to that, I've only been working with the Meraki for about 2 months now. Cisco stuff in general I'm familiar with.

Where is the "Captive portal strength" setting supposed to be?

[alemabrahao · Accepted solution]

Refer the documentation.

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Splash_Page

[cmr]

@AGomez it is under the Wireless/Access Control page under Advanced splash settings as below:

[AGomez]

cmr,

The documentation that alembraho listed says this:

The MX Splash Page feature is not currently compatible with the Active Directory integration. As a result, enabling Active Directory integration will cause Access Control/Splash Page not to appear in the menu.

Unfortunately for me, this is exactly how we have our mx-75 set up. Unless I'm missing something, looks like I'll just have to continue living with it. 😉