Solved! Go to Solution.
Hi,
if you use Microsoft's RADIUS ("IAS") the "Grant Remote Access" check box will decide if the RADIUS will send an accept or deny message for that user. Other RADIUS-request- and ADS-attributes - if defined - will be checked as well before sending the accept.
- Steffen
Wireshark will display a good interpretation of the RADIUS packets. It can capture data itself or can read TCPdump and other formats.
The reply-attribues depend on the profile configuration. You can add aditional attributes on the extendedprofile-tab.
We use different profiles to match against different request-attributes or ADS-group-memberships and add "Filter-ID" attributes for example to map them to specific roles.
-Steffen
Philly,
It doesn't sound like you have Radius configured for authentication? Do you have a Radius server pointing to AD for authentication? You might try searching the Steel Belted Radius docs to see if the RADIUS daemon can read this attribute from AD and use it for authentication. If you can define the "Grant Remote Access" flag as a standard RADIUS attribute or a Vendor Specific Attribute in RADIUS then you can use it to control access. But in order to do so you would need to configure the IVE to use RADIUS authentication and point to a RADIUS authentication server for this user realm.
Thanks for the input Luke. I, personally don't care to use the Dial-In tab. I just need to know if using that tab will send a Radius attribute, if I'm using Radius for authentication. I would prefer to use AD or LDAP and have them in a group but right now it is above me unfortunately.
:-)
Hi,
if you use Microsoft's RADIUS ("IAS") the "Grant Remote Access" check box will decide if the RADIUS will send an accept or deny message for that user. Other RADIUS-request- and ADS-attributes - if defined - will be checked as well before sending the accept.
- Steffen