HI Mike,
You sure can. Do something like this : (For an ODBC DB...but similar for
others)
AuthByPolicy ContinueUntilReject
<AuthBy SQL>
AuthSelect
DBSource dbi:ODBC:xxxx
DBUsername xxx
DBAuth xxxx
AccountingTable %Y%m
AccountingStopsOnly
## TABLE COLUMN ## NAS RESPONSE ##type
AcctColumnDef ACCTSESSIONID,Acct-Session-Id
AcctColumnDef USERNAME,User-Name
...
AcctColumnDef ASCENDXMITRATE,Ascend-Xmit-Rate,integer
AcctColumnDef ASCENDDATARATE,Ascend-Data-Rate,integer
</AuthBy>
<AuthBy NT>
Identifier NTSystem
Domain xxxx.xxx.xxx
</AuthBy>
(Or replace the last one with Unix or File or whatever)
Regards,
Anton Sparrius
-------------------------------------------------------
Smarter Way http://www.smart.net.au
Email [EMAIL PROTECTED]
Phone (03) 9846 1711
Melb 1800-240-829
Sydn 1800-888-761
-----Original Message-----
From: mike grommet <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, March 11, 1999 4:12 AM
Subject: (RADIATOR) Question: Authenticate by unix, but use SQL accounting?
>For management purposes, I would like to be able to keep my authentication
>working as it is with my unix users file, but I would like to
>store all accounting information, and session limit stuff in a SQL
>database...
>
>From reading the docs, it seems radiator can do this if I am doing authby
>SQL,
>but doesnt seem to include possibilities for this scenario... Am I missing
>something?
>
>
>It sure would be nice to be able to do queries to an sql database to check
>customer usage and such.
>
>I realize I could make an SQL database out of the unix password file, but I
>would prefer to not
>have to do this to achieve this functionality...
>
>
>
>
>
>===
>To unsubscribe, email '[EMAIL PROTECTED]' with
>'unsubscribe radiator' in the body of the message.
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
