On Mon, Nov 04, 2013 at 12:55:18PM -0800, Alan DeKok wrote:
Jakob Hirsch wrote:
sorry, I found another unlang oddity regarding return codes.
This shouldn't be different from 2.2.0.
So the "ok" gets processed, but the final return code is "updated", which makes FreeRADIUS reject the request, where it should be accepted (to my understanding).
This has to do with the return code priorities. The higher priority return code is the one which is kept.
Here, "updated" has higher priority than "ok". It's been that way since 0.9, IIRC.
In authenticate, they are all set to '1': https://github.com/FreeRADIUS/freeradius-server/blob/master/src/main/modcall... I would have though from that that the OK should immediately return (and therefore the updated=1 should be irrelevant)? Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>