Re: DB problems, again.

Kurt Schafer ( (no email) )
Mon, 20 Jul 1998 14:18:29 -0400

The only things being checked from MasterAccounts in that query you gave are
whether or not the account is active. The MasterAccounts table doesn't have
any fields for login, password, shell, etc.

Active = Active checkbox AND whether the account is expired in my definition
BTW. (not just the active check box)

- Kurt Schafer
- Network Administrator
- Cyber Beach Communications
- http://www.cyberbeach.net
- BOO !!

-----Original Message-----
From: Reid Sutherland <reid@isys.ca>
To: radiusnt@iea-software.com <radiusnt@iea-software.com>
Date: Monday, July 20, 1998 12:10 PM
Subject: DB problems, again.

>In the documentation it states that MasterAccounts has pretty much nothing
>to do with anything except for if the user is active or not. But I found
>something fun today. MasterAccounts is checked for almost everything. In
>other words, loginp, password, accounttype, and shell are all checked here.
>Any reason for this not being in the docs?
>If I removed these fields I had to create from the Masteraccounts, Radius
>will not auth the user.
>
>Here's a snipet I got from Radius in -x15 mode.
>
> SQL Statement: Select DateDiff('n', Now, DateAdd('d', ma.Extension+1,
>maExpireDate)), DateDiff('n', Now, DateAdd('d', ma.Extension+1,
>maExpireDate)), sa.AccountID, sa.AccountType, sa.Password, sa.Login,
>sa.Shell From MasterAccounts ma, SubAccounts sa Where (sa.Login='fitzgewi'
>or sa.Shell='fitzgewi') AND ma.CustomerID=sa.CustomerID and sa.Active<>0
and
>ma.Active<>0
>
>ODBC Error:00000:1074927752:
>
>
>Not Found in ODBC, Checking users file...
>
>Reid Sutherland
>Network Administrator
>ISYS Technology Inc.
>http://www.isys.ca
>Fingerprint: 6552 6469 5320 7475 6568 6c72 6e61 0a64
>
>