Wi-Fi client getting credential pop up 3-4 times a day

Devendra_Rajput
Comes here often

Wi-Fi client getting credential pop up 3-4 times a day

All users at site are getting WiFi credential pop up 3-4 times a day. we are using MS chap v2.

 

Devendra_Rajput_0-1771321155766.png

 

9 Replies 9
alemabrahao
Kind of a big deal
Kind of a big deal

Are you using an external RADIUS server, the one from Meraki?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Devendra_Rajput
Comes here often

Cisco ISE on Azure

alemabrahao
Kind of a big deal
Kind of a big deal

Check the session timeout on the policy result.

 

Cisco ISE default session timeout is 7200 seconds (2 hours), often managed via RADIUS attributes to force re-authentication. 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
alemabrahao
Kind of a big deal
Kind of a big deal

How is the session timeout configured?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
KarstenI
Kind of a big deal
Kind of a big deal

The main question is how you want to have it? When you write "MS-Chapv2", I assume that you are using 802.1X with PEAP here. The best way would be to go paswordless with certificates. With username/password there are multiple options how your supplicant can be configured:

  • Ask for credentials on every connect (which is likely what you have now)
  • Use Single Sign On with the AD credentials which can be cached for later authentications
  • Use stored credentials for the Authentication.

How should it be?

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
Devendra_Rajput
Comes here often

  • Use Single Sign On with the AD credentials which can be cached for later authentications
PhilipDAth
Kind of a big deal
Kind of a big deal

Maybe a year ago, Microsoft changed Credential Guard to block SSO for MSCHAPv2.  What you are seeing is now the expected behaviour.

 

You need to migrate to certificates to stop this.

 

https://www.keytos.io/blog/cloud-security/microsoft-disabled-ms-chapv2-for-network-sso-credential-gu...

 

Finiasferbikas
New here

Es hängt davon ab, wie wichtig Ihnen Sicherheit im Vergleich zu Komfort ist. Wenn Sie maximale Sicherheit wollen, ist passwortlos mit Zertifikaten ideal – keine Passwörter, die gestohlen werden könnten, automatische Authentifizierung. Bei der Nutzung von Benutzername/Passwort über cazimbos.de MS-CHAPv2/PEAP können Sie wählen: jedes Mal nach Anmeldedaten fragen (sicher, aber lästig), SSO mit zwischengespeicherten AD-Anmeldedaten verwenden (praktisch, relativ sicher) oder Anmeldedaten im Supplicant speichern (am wenigsten sicher, am bequemsten). Wägen Sie je nach Umgebung ab.

PhilipDAth
Kind of a big deal
Kind of a big deal

How can you use SSO with cached credentials? 

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.