(RADIATOR) authby radius

Wed Sep 10 11:30:23 CDT 2003

This is how I do it and it works great. The <AuthBy GROUP> in the realm
handler will continue to forward the acct packets to the end-point
Radius server after it writes to our local database. The AuthBy
GlobalAcct is the identifier for the <AuthBy SQL> that handles the local
database insert.

<AuthBy SQL>
    Identifier GlobalAcct
    IgnoreAuthentication

        DBSource dbi:Sybase:server=*******
        DBUsername ***********
        DBAuth ***********

	  ************
	  ************
</AuthBy>

<Handler Realm = /domain.com/i>  
  <AuthBy GROUP>
      AuthByPolicy ContinueAlways
      AuthBy GlobalAcct

        <AuthBy RADIUS>
                Host         202.202.202.9
                Secret       secret
                AuthPort     812
                AcctPort     813
                Retries      2
        </AuthBy RADIUS>
   </AuthBy>
</Handler>

Dave

-----Original Message-----
From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] On
Behalf Of tracker
Sent: Wednesday, September 10, 2003 8:49 PM
To: radiator at open.com.au
Subject: (RADIATOR) authby radius

Hi all,

Is it possible to store the accounting record of a user if my server 
just acts as proxy? If so, how?
Example, below is my config for the realm domain.com

<Realm domain.com>
        <AuthBy RADIUS>
                Host            202.202.202.9
                Secret          secret
                AuthPort     812
                AcctPort     813
                Retries         2
        </AuthBy RADIUS>
</Handler>

I want to have a copy of the accounting of users for domain.com and i 
will store it in mysql.

Thanks.

-- 
jaws
---------------
Computer system security is a journey, not a destination

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.