how to use groups within freeradius
Phil Mayers
p.mayers at imperial.ac.uk
Tue Jun 28 10:55:41 CEST 2011
On 06/27/2011 09:29 PM, Ken Felix wrote:
>
> Can anybody post a simple howto with regards to using groups within
> freeradius? What we would like todo is restricted some user from
> logging into various firewalls. I've created usergroups and defined
>
Which version of FreeRADIUS are you using?
Anyway, the group config you've written doesn't do what you want. All it
says is "if you're this username and coming from these IPs, you're in
the gruop".
You're not actually acting in the group membership.
There are lots of ways to do this, but personally I prefer to keep SQL
groups entirely user-based, and use huntgroups for NAS IPs, then compare
the two. So:
raddb/huntgrousp:
restricted NAS-IP-Address == 192.0.2.1
raddb/sites-enabled/xxx:
authozie {
if (Huntgroup-Name == restricted) {
if (SQL-Group == "restricted") {
# ok to login
}
else {
reject
}
}
}
...or if you prefer to us a "users" file, in raddb/users:
DEFAULT Huntgroup-Name == restricted, SQL-Group == "restricted"
Fall-Through = No
DEFAULT Huntgroup-Name == restricted, Auth-Type := Reject
Fall-Through = No
There are lots of other ways to accomplish this. The point being, you
need to actually check the group, and if you define the group so that it
depends on the username, and they thing they're permitted to access,
then you're essentially writing a whitelist and would need something
like, in your example, raddb/users:
DEFAULT SQL-Group == xxx
Fall-Through = No
DEFAULT SQL-Group == yyy
Fall-Through = No
DEFAULT Auth-Type := Reject
More information about the Freeradius-Users
mailing list