Hello Chris -
On Monday 19 March 2001 13:10, Chris M wrote:
> >> The only problem I forsee is, how do I make the SessionDatabase
> >> high-availability? In other words, is there a way to replicate
> >> the DB INSERTs and DELETEs so that auth or acct radiator
> >> processes talking to MySQL can h
Chris M wrote:
>
> >> The only problem I forsee is, how do I make the SessionDatabase
> >> high-availability? In other words, is there a way to replicate
> >> the DB INSERTs and DELETEs so that auth or acct radiator
> >> processes talking to MySQL can have entries simultaneously
> >> made in Sess
>> The only problem I forsee is, how do I make the SessionDatabase
>> high-availability? In other words, is there a way to replicate
>> the DB INSERTs and DELETEs so that auth or acct radiator
>> processes talking to MySQL can have entries simultaneously
>> made in SessionDatabases on two differe
Mike,
Thanks for the response. However, that would only work if I could
specify a different SessionDatabase per AuthBy clause within the same
Realm. But you can't. For example, it would work if I could do the
following:
AuthByPolicy ContinueUntilAccept
SessionDatabase SDB
Hello Kevin -
On Wed, 03 Nov 1999, Kevin Fowler wrote:
> Hello,
> We have multiple groups of customers authenticating out of multiple
> databases with some of the usernames being the same. They need to be
> able to authenticate with realms and without realms. The problem is with
> the Sess
Hi Kevin,
The default behaviour for the session databases is to log the _original_
username prior to any RewriteUsername
In that case of SQL SessionDatabase, it is easy to alter the configuration so
it uses whatever you want as the username. You would probably want to change
AddQuery and CountQu
