Security

last person joined: 22 hours ago 

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

Limit concurrent 802.1x users without CoA

This thread has been viewed 7 times
  • 1.  Limit concurrent 802.1x users without CoA

    Posted Jun 17, 2015 09:36 AM

    Hi,

     

    I know that Clearpass can limit the concurrent users with the same login on 802.1x. But I want to know if it is possible to do with a Access Point / Controller that doesn't support RADIUS CoA. It's possible?

     

    The customer has Fortinet controller and Access Point. Fortinet support RADIUS 802.1x auth and accounting but not CoA. 

     

    The scenario are:

    Users from Group1 can authenticate only on 2 devices with the same login simultaneously.

    Users from Group2 has no limit.

     

    Clearpass can solve this issue? 

     

    Best Regards,

    Paulo R.



  • 2.  RE: Limit concurrent 802.1x users without CoA

    EMPLOYEE
    Posted Jun 17, 2015 09:44 AM

    It really depends on how reliable the Accounting Stop packet is coming from Fortinet.

     

    If it is reliable, then because of the flixability of ClearPass we can write a custom SQL query to look at the number of active sessions that the username has. We use this information as authorization. Based on this information and depending on the capabilities of Fortinet, we could redirect the user to a page saying that there are too many devices connected to the network using this username.



  • 3.  RE: Limit concurrent 802.1x users without CoA
    Best Answer

    Posted Jun 18, 2015 10:54 AM

    Did a similar thing a while ago and believe the below SQL query was used to create the active_session attribute which can then be used during Authorisation:

     

    select count(*) as active_session from radius_acct where (username = '%{Authentication:Username}') AND end_time is null AND termination_cause is null AND (calling_station_id = '%{Connection:Client-Mac-Address-NoDelim}');

     

    As zjennings stated you need to ensure the Fortigate is reliable at sending RADIUS accounting.



  • 4.  RE: Limit concurrent 802.1x users without CoA

    EMPLOYEE
    Posted Jun 18, 2015 02:16 PM

    Good SQL query. Might I suggest you add a time constraint on the search based on max session timeout or at least limit the search to 24 hours.