Hello Jay -
You use AuthBy RADMIN in exactly the same way as AuthBy SQL.
You specify an AuthSelect statement in your Radiator configuration file
together with the appropriate AuthColumnDef's to do the Check's and Reply's.
You can use the table definitions for RAdmin as they are currently defined,
or define your own as you see fit.
<AuthBy RADMIN>
DBSource ....
DBUsername ....
DBAuth ....
AuthSelect .....
AuthColumnDef ....., check
AuthColumnDef ....., reply
.....
</AuthBy>
hth
Hugh
NB - I'm travelling for a couple of weeks ...
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
----- Original Message -----
From: "Jay West" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 29, 2000 1:02 AM
Subject: (RADIATOR) radmin help, additional check/reply items
> Ok, I'm probably being obtuse here, but I can't see the forest for the
trees
> ;)
>
> We're trying to convert from the default SQL database supplied with
radiator
> to the default SQL database supplied with radmin.
>
> There are several reply attributes that we use for every user (and they
are
> different for each user): FRAMED_FILTER_ID and FRAMED_NETMASK
>
> These are defined in the RADUSERS file. From what I've seen gazing through
> the code (I'm NOT a perl programmer) it would appear that by default these
> fields are not used (like they aren't in the default SQL database in
> radiator; in radiator you need to explicitly add an AuthSelect that pulls
> the CHECKATTR and REPLYATTR data for any extra items, the above two
> included). I want to basically do the same thing with the Radmin stuff. I
> was thinking you just need to specify an AuthSelect in <AuthBy Radmin> to
> return the additional fields, but the plot thickens....
>
> In AuthRADMIN.pm, it appears that they already modify the default
AuthSelect
> (is this perchance documented anywhere?) to include things like
> STATICADDRESS, MAXLOGINS, etc. This would make me think I just need to put
> in my own AuthSelect in the radius config file, but when looking at that
> code it has a comment about pulling extra things from RADCONFIG and
> RADATCONFIG. So... this makes me think I might be heading down the wrong
> path and not using something that might already be built in.
>
> So what do I need to do here to have radiator honor these fields in the
> radmin database.... just specify an AuthSelect that also selects things
like
> FRAMED_FILTER_ID and FRAMED_NETMASK, or do I need to hack up
AuthRADMIN.pm,
> or do I just need to add some stuff to the RADCONFIG and RADATCONFIG
tables,
> or a combination of the above? Hopefully I'm making SOME sense at least.
>
> Any help/advice is most appreciated!
>
> Jay West
>
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
