Posture and Remediation for Meraki NAD's

[Patrick Lloyd]

Hi Team,

I understand that the current flow for a guest in the Meraki NAD use case would be to the extent of:

1. User connects to meraki guest ssid and redirected to their LWA portal
2. User clicks on the don't have an account that launches to ise portal (perhaps in a new Window)
3. User creates an account on ISE and sponsor is notified to approve
4. User directed to close this page or provides link back to meraki redirect
5. Sponsor approves and user logs in after they receive credentials

I have a customer who is asking whether this will ever change, and whether we’re going to implement Posture and Remediation more than anything else on Meraki.  Is there an answer I can provide to them on that?

[howon · Accepted solution]

We currently support Meraki NAD for posture, but it requires customer to load beta code of Meraki. The customer will need to contact Meraki SE / Support team to get beta code loaded up. Below is snippet of beta GUI for ISE on Meraki:

[Jason Kunst]

Also see http://cs.co/ise-community under guest & web auth there are more examples

[Jeffrey Jones]

its so broken right now, you have to disable radius accounting on meraki to get posture compliance to work, Meraka (aka cisco) has not looked at the problem and there is currently no bugID or timeline on a fix.