I am using 1.16.45 and the SQL that is being generated is as follows:
Select DateAdd('d', ma.extension, maExpireDate), DateAdd('d', ma.extension,
maExpireDate), sa.AccountID, sa.AccountType, sa.Password, sa.Login,
sa.Shell From MasterAccounts ma, SubAccounts sa Where sa.Login='tony' AND
ma.CustomerID=sa.CustomerID and sa.Active<>0 and ma.Active<>0
This produces data for all accounts with user name "tony" with no
differentiation of passwords. Is this a version issue or am I doing
something wrong.??
tony
At 03:28 PM 3/4/97 -0800, you wrote:
>Tony Schwartz wrote:
>>
>> Can the user and passwd together make up the key so that they can be
>> queried as different records assumming they have different passwds?
>
>RadiusNT already does this.
>
>> I realize this probably violates some RFC but it would sure work cool for
>> people trying to bring together multiple user files.
>
>Only the front end enforces that. RadiusNT looks for the
>username/password
>match.
>
>--
>Dale E. Reed Jr. (daler@iea.com)
>_________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.emerald.iea.com
>
> ----------------------------------------------------------
> RadiusNT Mailing List listserver@emerald.iea.com
>