'Meraki Cloud Authentication' based SSID for Guest access. Self-registration - Allow users to create accounts Account authorization - Users must click a verification link in their email. (No need for sponsors) Let's say we advertise the same SSID across different branch offices/networks. The current behaviour is if a user creates an account in one branch, the user is not authorized to connect the same SSID in different locations. Meraki admins need to authorize the user manually. We have situations where the guests travel across different branches and it is now becoming a hassle to authorize them manually. Is there a way around this? I've looked into using 'Configuration Templates' which says: "MR access points can be managed and deployed in bulk using network templates. It may be helpful to group into common deployment types, such as retail locations or branch offices, so APs deployed at different locations all use the same SSIDs and authentication methods. This way, a user at one location can seamlessly join wireless networks at another location without needing to provide a different PSK or credentials." However, it doesn't mention the behaviour of Splash Users. I would appreciate any insights.
... View more
