Hello William -
You will need to specify two seperate AuthBy SQL clauses:
# define AuthBy clauses
<AuthBy SQL>
Identifier AccountingOnly
.....
IgnoreAuthentication
AccountingTable ......
AcctColumnDef ......
......
</AuthBy>
<AuthBy SQL>
Identifier AuthenticationOnly
......
AuthSelect ....
AuthColumnDef ....
.....
# no AccountingTable to disable accounting
.....
</AuthBy>
# define Handlers
<Handler .....>
# accounting AuthBy first, then authentication AuthBy
AuthByPolicy ContinueAlways
AuthBy AccountingOnly
AuthBy AuthenticationOnly
.....
</AuthBy>
This topic has been discussed many times on the mailing list:
www.open.com.au/archives/radiator
regards
Hugh
On Friday, Feb 14, 2003, at 06:42 Australia/Melbourne, William Taylor wrote:
NB: I am travelling this week, so there may be delays in our correspondence.Is there a way to Authenticate users out of one SQL database and insert the accounting records into a different database?I would like to have a seperate ACCOUNTING database and it doesn't look like I can right now. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
