make Radius more configurable in AAF so that attributes can be changed / configured

by: Frank S. | over a year ago | Integrations

Comments

• Frank, Can you supply the attributes that you believe would be useful. There is an extensive list and clearly not all of them would be appropriate. Troy

  by: Troy D. | over a year ago

• Hi Troy, unfortunately this and another both requested this option and both of them request different things.
  They would also be fine with the fact of AAF just forwarding the received attributes, so the client side, esp. a locally installed software can interpret the attribute and handle it in a dedicated matter.
  For instance: customer A needs AAF to either forward the radius attribute "Filter-ID" or to make this attribute configurable inside AAF.
  Thanks, Dan

  by: Daniel S. | over a year ago

• Scheduling this now

  by: Troy D. | over a year ago

• Cisco AnyConnect expects radius attribute 25 (Class) for VPN Profiles/Groups instead of filter-id

  by: E V. | over a year ago

• Checkpoint also expects radius attribute 25 (Class) for VPN Profiles/Groups instead of filter-id

  by: Michael P. | over a year ago

• Cisco ASA expects radius attribute 25 (Class) for VPN Profiles/Groups instead of filter-id

  by: Florian L. | over a year ago

• Hi, we want to replace our free-radius, which is used for dynamic-vlan-management. So, AAF-radius should use our LDAP-edir to read workstation objects and the ou of these objects. Our switches use it to tag the ports into the right vlan- segments.
  AAF must offer configurations, like this, into the admin-portal.

  by: Danny B. | over a year ago

• Danny, please add a separate request for the above. It has to do with ports and the initial request is for attributes. These are different requirements. Thank You, Troy

  by: Troy D. | over a year ago