Skip to content
This repository has been archived by the owner on Sep 10, 2020. It is now read-only.

Default freeradius 3 POSTAUTH query fails #26

Closed
nemesifier opened this issue Jul 11, 2017 · 0 comments · Fixed by #28
Closed

Default freeradius 3 POSTAUTH query fails #26

nemesifier opened this issue Jul 11, 2017 · 0 comments · Fixed by #28
Assignees
Labels

Comments

@nemesifier
Copy link
Member

Output of freeradius -X when trying a dummy authentication, eg: radtest admin admin localhost 10 testing123.

(5) sql: EXPAND INSERT INTO radpostauth (username, pass, reply, authdate) VALUES('%{User-Name}', '%{%{User-Password}:-Chap-Password}', '%{reply:Packet-Type}', NOW())
(5) sql:    --> INSERT INTO radpostauth (username, pass, reply, authdate) VALUES('admin', 'admin', 'Access-Reject', NOW())
(5) sql: Executing query: INSERT INTO radpostauth (username, pass, reply, authdate) VALUES('admin', 'admin', 'Access-Reject', NOW())
rlm_sql_postgresql: Status: PGRES_FATAL_ERROR
rlm_sql_postgresql: 23502: NOT NULL VIOLATION
(5) sql: rlm_sql_postgresql: ERROR:  null value in column "created" violates not-null constraint

In this case I think the best option is to keep the default postauth table as close as possible to what the default freeradius configuration expects.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants