Hi Mike and Hugh,
Firs thank you for your help.
OK, As you say ODBC is the best way in my case, to authenticate agains a MS
SQL 7.0 server.
Of course I need first to load (PPM>install DBI and PPM>install DBD-ODBC)
and define a DSN.
But I have two questions jet:
I read examples /goodies, common_sql.cfg, freeside.cfg. interbiler.cfg and
radp.cfg and I can not undertand:
1- They have not an AuthSelect. How must you configure your AuthSelect to
authenticate porperly a user agains a MS SQL 7.0 database?
I think you need to check if
- The login exist
- The check items are mached ( User-password, Connect-Rate, Nas-Port-Type,
Called-Station-id...).
- Get the reply items to give an IP, netmask, Frame-Protocol, etc.
Is it right somethink like this:
DBSource dbi:ODBC:radius
DBUsername admrad
DBAuth xxxx
AuthSelect select PASSWORD, IP, Frame-Protocol /
from USERSDB where /
USERNAME=�%n�and Connect-Rate=�28800� and / Called-Station-id=�943319100�
Sorry but I can not undertand. You need to search ( pass and check items)
and get the reply items to send them to the NAS
Have anyone and example?
2- And what about the database table? what field does it need? I mean that I
need to store check and reply items, does not ii? How?
Have anyone and example?
Thank you again for your help.
Best regards,
Fernando Mrat�n
12:23 19/01/00 -0500, you wrote:
>On Jan 19, 10:13am, Hugh Irvine wrote:
>> Subject: Re: (RADIATOR) Authentication over MS SQL 7.0
>>
>> Hello Fernando -
>>
>> On Wed, 19 Jan 2000, Fernando Martin wrote:
>> > Hi all,
>> >
>> > I think this questions is just very answered, but I need some information.
>> >
>> > Actually I have a NT 4.0 SP5 with Radiator 2.14.1 ( with patches 2.14.1)
>> > running properly, but I autherticate with a flat file. because of I have
>> > many users I need another way to do that, and I think MS SQL could be one
>of
>> > the best.
>> >
>> > I have read the manula pag 82, 107..and I know that:
>> >
>> > - I need to install DBI ( PPM>install DBI
>> > - Then, search the right module/driver to connect database.
>> > In my case I think I need ODBC because my MS SQL server is into another NT
>> > server that Radiator. So PPM>install DBD-ODBC.
>> >
>> > Is it right? Is there another way better? May be mSQL? Why?
>> > Is the ODBC conector stable?
>> >
>> > - I need to create the database into SQL server...
>> > - I need to configure my radius.cfg to authenticate
>> > and also create a System DSN into my Radiator server ( In my case
>> > DSN=Radius)to connect database
>> > ....
>> > ........
>> > <<Realm DEFAULT>
>> > PasswordLogFileName %L/%d-%m-%y-password.log
>> > AuthByPolicy ContinueAlways
>> > <AuthBy SQL>
>> > # Data to open database. DSN= radius
>> > DBSource dbi:ODBC:radius
>> > DBUsername admrad # login to connect
>> > DBAuth xxxx # pass to connect
>> > Is it all ok until this point?
>> >
>> > AuthSelect select PASSWORD from USERSDB where
>> > USERNAME=�%n�
>> >
>> > I do not know what I need to put here ( select...) to authenticate properly
>> > a user and also check his check items ( like Called-station-id, NAS-port,
>> > Acct-Status-Type, etc) agains the SQL. I think I need to configure my
>Radius
>> > databese and table USERSDB with login, pass, and check items... How to do
>> > that? Any example?
>> >
>> > # This enables accounting
>> > AccountingTable ACCOUNTING
>> > AcctColumnDef USERNAME,User-Name
>> > AcctColumnDef TIME_STAMP,Timestamp,integer
>> > # etc....
>> > </AuthBy>
>> >
>> > </Realm>
>> >
>>
>> You are definitely on the right track with everything you mention above. The
>> best place to start with SQL is in the goodies directory included in the
>> Radiator distribution. You will find example SQL table definitions, SQL table
>> creation scripts, and SQL configuration files. You can use these exactly as
>> they are, or you can use them as a base from which to add your own extra
>> features. Also have a look at the radius.cfg file in the main Radiator
>> directory to see a very detailed and documented configuration file which
>> includes various SQL definitions.
>
>Also, if you are on NT, wanting to talk to SQL on another NT, then DBD-ODBC is
>the best way to go.
>
>We usually prefer mysql to MS-SQL, but the ODBC connector to mysql on NT is
>still not terribly stable when used with Perl, so probably MS-SQL is best for
>you if you can afford it.
>
>I sent some patches to the mysql ODBC connector authors, but I dont know if
>they have been incorporated yet.
>
>Cheers.
>
>
>
>>
>> hth
>>
>> Hugh
>>
>>
>> --
>> Radiator: the most portable, flexible and configurable RADIUS server
>> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
>> Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
>> NT, Rhapsody
>>
>> ===
>> Archive at http://www.thesite.com.au/~radiator/
>> To unsubscribe, email '[EMAIL PROTECTED]' with
>> 'unsubscribe radiator' in the body of the message.
>>-- End of excerpt from Hugh Irvine
>
>
>
>--
>Mike McCauley [EMAIL PROTECTED]
>Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW
>24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
>Phone +61 3 9598-0985 Fax +61 3 9598-0955
>
>Radiator: the most portable, flexible and configurable RADIUS server
>anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
>Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
>NT, Rhapsody
>
>
Fernando Mart�n
Dpto. T�cnico
Interlinea 2000 Comunicaciones, S.A.
Gabiria, 2 - Edif. Serv�cios - Local X
20.305 Ir�n - Gipuzkoa
Telephone:(+34) 943 621033
Fax :(+34) 943 627340
�
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
