Security

last person joined: 7 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

Authentication Source - Role / Attribute

This thread has been viewed 10 times
  • 1.  Authentication Source - Role / Attribute

    Posted Oct 31, 2019 02:11 PM
      |   view attached

    Dear Experts 

     

    Please refer to attached snap. Can someone shed some light as to why we select/enable a particular field as Role and/or Attribute. What is the meaning of Role / Attribute here?

     

     



  • 2.  RE: Authentication Source - Role / Attribute

    Posted Nov 01, 2019 05:05 AM
    When role is ticked it's mapped directly to a ClearPass role. An attribute would need role mapping to achieve the same result.

    In your example if role is ticked, when a user authenticates, their department would become one of their clearpass roles.


  • 3.  RE: Authentication Source - Role / Attribute

    Posted Nov 01, 2019 09:31 AM

    Dear JR, 

     

    Just to understand, when you said "In your example if role is ticked, when a user authenticates, their department would become one of their clearpass roles", do you mean that this role will become one of the assigned roles? like [user authenticated]?



  • 4.  RE: Authentication Source - Role / Attribute
    Best Answer

    Posted Nov 01, 2019 09:47 AM

    Yes, that's correct.



  • 5.  RE: Authentication Source - Role / Attribute

    Posted Nov 01, 2019 10:22 AM

    Oh nice, let me check and share my feedback



  • 6.  RE: Authentication Source - Role / Attribute

    Posted Nov 02, 2019 04:30 PM

    very nice !



  • 7.  RE: Authentication Source - Role / Attribute

    Posted Nov 01, 2019 05:07 AM

    When you enable it as role, you will see departement value as a role in your authentcation, you can use it directly in enforcement profile.