Unable to authenticate freeradius using PostgreSQL
ross.mcowat at first-utility.com
Wed Nov 29 17:28:35 CET 2006
Thanks Kevin - you were right, the issue was with the SQL query in
postgresql.conf. I replaced my existing file with a default file on
another server, and everything worked fine.
Many thanks for your help!
freeradius-users-bounces+ross.mcowat=first-utility.com at lists.freeradius.
[mailto:freeradius-users-bounces+ross.mcowat=first-utility.com at lists.fre
eradius.org] On Behalf Of Kevin Bonner
Sent: 29 November 2006 16:16
To: FreeRadius users mailing list
Subject: Re: Unable to authenticate freeradius using PostgreSQL
On Wednesday 29 November 2006 05:52, Ross McOwat wrote:
> radius_xlat: 'SELECT id, UserName, Attribute, Value, Op
> #?authorize_check_query = '
> rlm_sql (sql): Reserving sql socket id: 4
> rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op
> #?authorize_check_query =
> rlm_sql_postgresql: Status: PGRES_FATAL_ERROR
radius_xlat now shows the query, but "SELECT id, UserName, Attribute,
Op" is not a valid SQL query. The "authorize_check_query" being listed
the radius_xlat line means that you haven't properly quoted the SQL
the config file. Look at the default postgresql.conf to see what you're
missing... paying close attention to quotation marks.
> I have changed the 'value' and 'op' columns around, as the
> authentication sql query within postgresql.conf appears to try and
> retrieve 'value' before 'op'. Using the supplied database schema, the
> op column appears BEFORE value. Not sure if this is significant or
> Or possibly the actual data format I've entered is incorrect? I
> (hope) it's something as simple as that.
It doesn't matter how the table columns are arranged, as long as your
asks for them in the correct order.
More information about the Freeradius-Users