Re: (RADIATOR) RewriteUsername

2002-02-28 Thread Ronan Eckelberry, Network/Systems Admin
    Try naming the realm DEFAULT.  It looks at anything after the @ to determine the realm name.  So, if a customer logs in as [EMAIL PROTECTED], it is going to look for a realm called .  By default, if Radiator finds no matches, it will try to use .   -Ronan   - Original Message

Re: (RADIATOR) AcctSQLStatement

2002-02-24 Thread Ronan Eckelberry, Network/Systems Admin
Cool. thanx for the info Hugh. One other question thoughwould I still get the same result if I changed the AuthByPolicy to ContinueUntilAccept? -Ronan - Original Message - From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "Ronan Eckelberry, Network/Systems Adm

Re: (RADIATOR) AcctSQLStatement

2002-02-24 Thread Ronan Eckelberry, Network/Systems Admin
I have it in the AuthBy SQL Clause. I don't see it executing in a trace though. Maybe I am typing something wrong. Here is a snip from the config: Description Default Realm for authenticating users RejectHasReason RewriteUsername s/^([^@]+).*/$1/ SessionDatabase RADONLINE AuthBy

Re: (RADIATOR) User-Name encrypted

2002-02-21 Thread Ronan Eckelberry, Network/Systems Admin
That's rightI knew it was a config change, but I couldn't remember what it was. Missed it when looking through all the old backup configs... -Ronan - Original Message - From: "Fabio Nitti (TEI)" <[EMAIL PROTECTED]> To: "Ronan Eckelberry" <[EMAIL PROTECTED]>; "Hugh Irvine" <[EMAIL