WLC Radius Credentials Caching

Unanswered Question
Jul 25th, 2007
User Badges:

We are using PEAP with ACS/AD as the external Database. The issue or behavior that we are experiencing is that clients require a Cached AD Token for the user authenticate against for the first time. The Client does not get an IP until authenticated and therefore cannot contact the DC.

We have shared laptops an its not feasible to cache all AD profiles(Tokens) to the laptop.

Will the Radius Authentication Server - Credential Caching option help by caching authenticated client sessions to the WLC and allow user to authenticate against multiple laptops? Is the above behavior correct(cached Token required)? Is there another approach to authenticating shared resources with PEAP/Radius(ACS)/AD

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Mike Lydick Tue, 07/31/2007 - 13:33
User Badges:

I have Radius Authentication working. I even have Active Directory being used as the external database for clients. The problem is that a user that never has logged into a laptop(configure for AD) get as Domain not available if we try the via wireless for that users first login. I fully understad the issue which is the client have not been issued an IP because they have not been authenticated.

More than likely there is not a workaround for this scenerio other than login via wireless with the new AD user credentials. In effect caching the AD profile locally.

What I would like to address is because my users are Transient (nurses and doctors that share laptops) is how to lessen number of time for a wired loggin by caching the AD account in at the WLC. I may be off base to the function of this feature but its not very well documented (from what I have found)

hrios Wed, 08/01/2007 - 09:31
User Badges:

I know what you are talking about. We use PEAP-MSCHAPv2 with machine authentication and it works great. Brand new user that has never logged on to the wireless computer can get authenticated.

Mike Lydick Thu, 08/02/2007 - 16:50
User Badges:

Yeah I would imagine machine authentication would be a better approach but that require issuing a cert to the machine. We are trying keep the hands on time with the laptops to a minimum and not to add yet another server for wireless security. We are not running any CA other than the ACS (self-signed cert). Even with that we are not adding the cert to the client list. I guess I will hit TAC up on the radius cache functionality. Also reconsider the security method we are using.

hrios Thu, 08/02/2007 - 16:59
User Badges:

PEAP requires server-side certificates only. No certificates on the client side

Mike Lydick Thu, 08/02/2007 - 17:01
User Badges:

Machine authentication? Do you have a White-paper on that (how-to)?

Mike Lydick Thu, 08/02/2007 - 17:15
User Badges:

Both of these show using (client-side certificate validation)certificates. Did you choose not to validate on the clients or how did you address this part of the client config?

Btw thanks for your response.

hrios Thu, 08/02/2007 - 17:29
User Badges:

Assuming your clients are Windows and/or Mac,the root CA certificates of many third-party CAs are already included in the OS. If your Radius server certificate is from a third-party CA that corresponds to an included root CA certificate, no additional wireless client configuration is required.


This Discussion



Trending Topics - Security & Network