Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

Restricting captive portal to 802.1x devices

This thread has been viewed 0 times
  • 1.  Restricting captive portal to 802.1x devices

    Posted Jun 28, 2018 03:42 AM

    Setup :Two SSID's, one is 802.1x for corp devices and another is Captive Portal for guest.

     

    Requirement : 802.1x connected devices should not get captive portal if they try to connect guest network.

     

    Tried solution where Endpoint attributes are created and applied rules to restrict/deny connection but, a guest account is getting created before denying access in guest database. This guest account should not be created even though access is getting denied. Is there any way to restrict captive portal?



  • 2.  RE: Restricting captive portal to 802.1x devices

    Posted Jun 28, 2018 04:24 AM

    This is very easy to accomplish.

     

    When on 802.1x - you need to update the endpoint with a new attribute type "isCorpDevice" = true.

     

    For Guest auth you have to use endpoint database as authorization source, and add a test for "isCorpDevice" = true, then trigger a profile that denies access or whatever you want done.



  • 3.  RE: Restricting captive portal to 802.1x devices

    Posted Jun 28, 2018 05:22 AM

    thanks john for reply

     

    The suggestion works. we were able to restrict access but every time corp device try to register as guest, a new guest account is getting created. The netwok restriction happens after guet registration. So we wan't to restrict registraton page.

     

    any solution?



  • 4.  RE: Restricting captive portal to 802.1x devices
    Best Answer

    Posted Jun 28, 2018 06:54 AM
    Your goal is to avoid that corpdevices land on Clearpass Captive Portal right?

    Guest networks usually have mac-auth. It is here you need to return a different role instead of just deny access. Deny access means your device gets the default guest-logon role.

    So - create a new role on the controller that doesnt have Captive Portal, create a cp policy for it and return this one in your macauth service for corpdevices.

    Would that work?


  • 5.  RE: Restricting captive portal to 802.1x devices

    Posted Jun 28, 2018 07:46 AM

    This is the exact solution we required. Thanks john