Hello Sven -
It is very simple to do what you describe (and its not dirty at all...):
# define AuthBy clauses
<AuthBy LDAP2>
Identifier LDAPAuthentication
.....
</AuthBy>
<AuthBy SQL>
Identifier SQLAccounting
.....
# empty AuthSelect to disable authentication
AuthSelect
# configure accounting
AccountingTable ACCOUNTING
AcctColumnDef .....
......
</AuthBy>
<AuthBy GROUP>
Identifier DoAuthenticationAndAccounting
AuthByPolicy ContinueAlways
AuthBy SQLAccounting
AuthBy LDAPAuthentication
.....
</AuthBy>
# define Realm(s) or Handler(s)
<Handler ....>
.....
AuthBy DoAuthenticationAndAccounting
.......
</Handler>
.......
If you have any other questions, please feel free to ask.
regards
Hugh
On Thu, 16 May 2002 20:54, Sven Holz wrote:
> Hi List
>
> Following Situation:
>
> We're going to setup LDAP for authentication running on Linux.
> Session- and Accounting Data should be written to a MySQL-Database.
>
> If I understood the Docu of radiator correctly, accounting on MySQL is
> just possible when authentication is done by MySQL also.
>
> Is this correct?
>
> So my question, if it is like that, is how can i solve the problem, LDAP
> is really important for us, because of many other systems with
> LDAP-Interfaces.
>
> Every solution (even dirty ones ;-) are highly welcome.
>
> Thanks a lot
>
> with kind regards || Mit freundlichen Gruessen
>
> Sven Holz
--
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.
