Security

 View Only
Expand all | Collapse all

Clearpass Enforcement based on the AD OU attributes

This thread has been viewed 63 times
  • 1.  Clearpass Enforcement based on the AD OU attributes

    Posted Apr 08, 2025 04:31 PM

    Hi, 

    We currently AD authenticated machines are being assigned Corp VLAN but  now some of these devices are now required to join a different VLAN based on the AD attributes. 

    I understand I can use OU for these devices where these devices will be added in specific OU in AD and then we can use that as a match criteria as below :

    Type: Tip Name :Role EQUALS  Value: Machine Authenticated

    AND

                                                  Type: Authorization:AD Name Name: UserDN CONTAINS  Value: OU=Restricted_New

    Please let me know if this works?

    I would also like to know that if AD is actually passing this attributes to Clearpass because in Access tracker Live logs I am not seeing UserDN in the input attrbutes of the machine?

    These are the attributes machine is passing as an input

    Thanks in advance

     



  • 2.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 09, 2025 12:49 AM

    Hello , can you show the service because i assume you didn't put AD as authorization source thats why Clearpass not fetch this attributed from AD




  • 3.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 09, 2025 01:01 AM

    Hi , 

    Do you mean this option ?

    Yes , it not enabled but we have, Authentication pointing on the next page to AD. 

    If we enable that Authorization in existing service, will it have any impact? Anyways I am going to create a new service for this enforcement I can enable Authorization, but again will it have any impact on other policies?

    Thank you in advance. 




  • 4.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 09, 2025 01:06 AM

    Hello Exactly this option and put you AD there . You can create aditional service to point on specific switch or specific controller where you can test it , on that way it will not have impact on the rest .




  • 5.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 09, 2025 01:19 AM

    Ok perfect, I am going to have a separate OU created for testing and only move couple of clients in that OU. I hope this approach will not have any impact as if this enforcement rule does not match it will move to the next policy. 
    Now once that matching test is done, next I would like to add same condition to existing wireless policy to deny access based on the same match so that machine would not connect to Corp network, will that have any impact?  I think I will need enable 'Authorization' on existing policy as well.
    The whole idea is to restrict some of the already AD authenticated clients to separate VLAN, so they should not be able to connect Corp even if they manually try to connect corp wireless SSID which they will be able to if I don't them using match criteria as specific OU.

    Thanks a ton.

     




  • 6.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 10, 2025 03:37 AM

    Hi , I would like to just to know if there will be any impact if we enable authorization on existing server? I will be touching existing service which has several users connecting using just role 'Machine Authenticated'.




  • 7.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 14, 2025 01:13 AM

    Hi,

    no, enabling authorization does not impact authentication. You also do not need to enable the "authorization" check box unless you want to use sources for authorization additional to your authentication sources. So every authentication source will automatically be used for fetching authorization attributes as well.

    Also regarding your first question: The UserDN attribute is showing under "Authorization Attributes", not "Computed Attributes". Please check there. As far as I can tell from your screenshot you are looking under "Computed Attributes".

    Last but not least, your matching criteria for your enforcement policy looks fine. I configured something similar with TLS authentication and it worked out well. Have you tried already?

    Best,

    Levi




  • 8.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 14, 2025 01:52 AM

    HI Levi, 

    Thanks for the response, no I have not tried it. I will try soon and let you know if that works.

    Regarding  Authorization Attributes, I don't see that option , see below screenshot
    Probably because I don't have Authorization enabled, so questions was will I be able to use userDN without enabling Authorization?




  • 9.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 15, 2025 05:54 AM

    Hi,

    no, you do not need to enable authorization in the service to see those attributes. 

    What does the configuration of your authentication source look like? What attributes are you fetching?

    You can test your filter queries under Authentication - Sources - <your-ad> - Attributes. Click on the authentication filter and switch to the "Attributes" tab and test one of your computer accounts. For the username please use the value of the following attribute from your access tracker entry: Computed Attributes - Certificate:Subject-CN. Click on Execute on check wether you get any account in return or not.

    When you do not get any return you may have to adjust your attribute filter query. 

    Best,

    Levi




  • 10.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 15, 2025 08:49 AM

    HI Levi, 

    I am not sure where you want me to do that testing but I see below settings in Authentication attributes:

    I would like to use OU of user's machine to apply enforcement profile, so by looking at these attributes I was thinking to use userDN which was suggested by other posts. 
    This is an existing set up and there are lot of users/devices using clearpass for authenticating, so I don't really want to change any existing settings in this. 




  • 11.  RE: Clearpass Enforcement based on the AD OU attributes

    Posted Apr 17, 2025 07:51 AM

    Hi, 

    So I tried it myself once:
    I didn't know this either, but apparently you have to query something from your authorization source in the enforcement policy or in the role mapping for the authorization attributes to appear in the access tracker. If you simply query whether the client holds the tips role "Machine Authenticated", no authorization attributes are displayed.
     
    In other words, simply set up your enforcement policy as you asked at the beginning of this discussion. As this is productive enviroment, create a test service and configure a condition for this service to match. For example, that the authentication takes place on a specific switch port. You can then test your new service on this port without it becoming active for other clients.
    Then test authentication against this service. You should then see the authorization attributes you are looking for appearing in the access tracker entries.
    As mentioned, you do not need to check the box for "Authorization" in the service itself.
     
    Best,
    Levi