Skip to Content.
Sympa Menu

assurance - [Assurance] RE: Has anyone looked at using InCommon Silver accounts to access a secured wireless network?

Subject: Assurance

List archive

[Assurance] RE: Has anyone looked at using InCommon Silver accounts to access a secured wireless network?


Chronological Thread 
  • From: Brian Arkills <>
  • To: "" <>
  • Subject: [Assurance] RE: Has anyone looked at using InCommon Silver accounts to access a secured wireless network?
  • Date: Thu, 8 Sep 2011 15:34:07 +0000
  • Accept-language: en-US

There also may be issues of when a user changes their password, for a time the 802.1X client may be trying to use the old password and causing the account to be temporally suspended. Does anyone have ideals of how to best mitigate this?

[BA] If AD is behind the authentication here (which you've indicated), then the "old" password is still accepted as valid for a limited period of time after a password change, if NTLM is used (which extends to NTLMv2 and simple/basic bind). The period of overlap is by default an hour, but is configurable: http://support.microsoft.com/kb/906305. So whether your question constitutes something that actually happens depends on whether the time the 802.1X client caches the old password is longer than that AD overlap period.




Archive powered by MHonArc 2.6.16.

Top of Page