Assurance

[Russell J Yount <>]

Has anyone looked at using InCommon Silver accounts to access a secured wireless network?

Our network group is using a Windows RADIUS server to accept Windows AD passwords for access to a secure wireless network.  The 802.1X authentication shown by the windows client is “protected EAP (PEAP)” with “Secure Password (EAP-MSCHAP v2)”.

If we secure the Windows AD to comply with InCommon Silver requirements will we be able to continue using this configuration? If not, can anyone suggest a good alternative which would continue to permit use of user passwords to access the wireless network?

The Windows, Mac, and Linux wireless clients are storing the user’s password so the wireless client may roam and re-authenticate.  Is this acceptable in InCommon Silver?

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?

-Russ

Russell J. Yount

Identity Services, Carnegie Mellon University