I've always believed that you start with what you know and work from that stance. After I get to know freeRADIUS better I may determine that LDAP, or whatever else, is a better solution.
For the time being this is the route we have chosen. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:freeradius-users-admin@;lists.cistron.nl] On Behalf Of > Guillermo Schimmel > Sent: Thursday, November 07, 2002 12:12 PM > To: [EMAIL PROTECTED] > Subject: Re: MSSQL and FreeRADIUS > > > May I ask why? > > You have excelent choices out there, i.e. LDAP. > > > > Brian Johnson wrote: > > > I am looking to create a completely custom user system database > > backend for FreeRADIUS. I was wondering if there is a doc on the > > variables that may be used in the SQL queries specified in the > > mssql.conf file. I would like to pass the username and the > NAS address > > or other identifier to a stored procedure on the SQL server > and then > > give the output in the format desired by the module. > > > > If anyone has already done this, please tell me where to go > for the 411. > > > > TIA > > > > _______________________________ > > Brian Johnson > > Internet Operations Specialist > > Northern Valley Communications > > "Let's Roll!" - Todd Beamer > > > > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
