Wireless Access

last person joined: 14 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Enforce Machine Auth with different aaa profiles?

This thread has been viewed 0 times
  • 1.  Enforce Machine Auth with different aaa profiles?

    Posted Feb 22, 2016 04:34 PM

    I think this may be a non-starter, but posting here to see if anyone has this sorted.

     

    Environment:

    Master-Local controllers 7210s, running ArubaOS 6.4.2.14-FIPS

    AP-135

    RADIUS - NPS on Server2012

     

    Our users have smart cards, and we are doing EAP-TLS authentication via RADIUS. Currently, we are only authenticating the user. In our environment, we have a requirement to make sure that only known laptops connect to the wireless. Also in our environment, we do not have automatic certificate enrollment for Active Directory machines, so there are no computer certificates.

     

    So what I'm looking for, is a way to enforce machine authentication, to ensure that only our known machines can connect (it's possible for a user to take a CAC-enabled home laptop, configure the SSID, and get on). My fear is that we may have to resort to MAC authentication for the machine side, which is not all that great.

     

    In a perfect world, we could enforce machine authentication using EAP-PEAP/MS-CHAP-V2 802.1x for the computer, and then authenticate the user with EAP-TLS using their smartcard.

     

    I should mention that we are using the built in supplicant in Windows 7 (configured via Group Policy), and that we do not have ClearPass (or the funds to purchase). And the Windows 7 WLAN configuration looks like you can choose either EAP-TLS or EAP-PEAP, but not both.

     

    Can we achieve this with what we've got on hand?



  • 2.  RE: Enforce Machine Auth with different aaa profiles?

    EMPLOYEE
    Posted Feb 22, 2016 04:49 PM
    Unfortunately, you'll have to rely on MAC-authentication as the supplicant
    can't do split EAP types for machine + user.