Meraki

Shane3 · ‎Aug 22 2019

In regards to point #2: Now that I think about what you mean by that specific point more, I am going to simply say no. I can't see the possibility of google auth working in this way when using the Meraki cloud. )-:

Shane3 · ‎Aug 20 2019

Giovanni, 1) Unfortunately this wont work. 2) Not with Meraki Devices alone. 3) This seems like it would work if ISE supports it but your interpretation of limitations sound correct. I know that I didn't necessarily provide a solution but hopefully this helps by eliminating the options that definitely won't work.

Shane3 · ‎Aug 5 2019

Hi everyone, 1. The user field is solely for the user ID info pulled from AD when active directory integration is present. The other visibility things mentioned here are good points and ripe for a feature request (make a wish) (-: 2. It is expected behavior that the user can reconnect with the same "credentials" on the splash page within the time duration allotted without another email being sent to the admin. One can imagine the situations where that would be useful. 2.5. If the user can reconnect with the same "credentials" outside of the sponsorship duration, without an auth email being sent to admin, please open a support case. This is not expected behavior. You can reference the below article for point #2: https://documentation.meraki.com/MR/Encryption_and_Authentication/Sponsored_Guest

Meraki

Community

About Shane3

Shane3

Community Record

Badges

Re: Wireless Guest access (Google authentication splash) and Google identit...

Re: Wireless Guest access (Google authentication splash) and Google identit...

Re: Sponsored Guest - returning users auth problem

Re: Sponsored Guest - returning users auth problem