> From: "Tom Emerson" <[EMAIL PROTECTED]>
> I'll jump in here with a suggestion -- it took a while for it to sink in for
> me, so perhaps this will help someone else stay afloat...
Thanks for the jump!
> You can "fake it" somewhat with
>
> SELECT id,user as username,"Password" as attribute,
> password as value,"==" as op
> FROM ${authcheck_table}...
>
> in this example, I'm presuming actual field names of "user" and "password",
> which need to correspond to the names "username" and "value" as required by
> the internals of the program [err, hope I have that part right] Likewise,
> this returns hard-coded field values of the word "password" and an operator
> of "==" for the attribute and op fields.
Yes, this is the last thing left to be clarified - whether the module reads data from
the database as hash with hardcoded field names, or its just a row, in which case the
position of fields in SQL reply is important. Anyway, it's possible to satisfy both at
the same time.
Thank you very much for your help!
--
Best Regards,
Sinisa Burina
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
