How freeradius responds in json format to the request to authorize
aland at deployingradius.com
Wed Jul 26 20:55:14 CEST 2017
On Jul 26, 2017, at 2:46 PM, Fiorella De Luca via Freeradius-Users <freeradius-users at lists.freeradius.org> wrote:
> Regarding checks like bandwidth limits and session time limit, when authorizing through a REST API, I guess we can do these checks in the authorization phase via the REST API too and return an appropiate response accordingly, is this correct?
The REST back-end can do pretty much anything it wants with the data it gets, and it can return pretty much any data in response.
FreeRADIUS can then use that response to set RADIUS attributes.
> check the user exists, check password matches, check user has not exhausted their allocated daily bandwidth.
More information about the Freeradius-Users