Thor Spruyt wrote:
> I now found a way that seems to work. I created an additional sql { }
> and added it to the authorize section.
> The seems to work, but I'm wondering if it's a good way to do this or
> are there better ways?Huh... I found something nice accidentally... rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op ??FROM radcheck2 ??WHERE Username = 'thor' ??ORDER BY id rlm_sql_postgresql: Status: PGRES_TUPLES_OK rlm_sql_postgresql: affected rows = rlm_sql: The 'op' field for attribute 'User-Password = xxxxxxx' is NULL, or non-existent. rlm_sql: You MUST FIX THIS if you want the configuration to behave as you expect. So leaving the op field empty will result in FreeRadius trying to match both retrieved passwords! Am I doing something stupid here? -- Regards, Thor Spruyt E: [EMAIL PROTECTED] W: www.thor-spruyt.com M: +32 (0)475 67 22 65 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
