[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freeradius-users
Subject:    Re: How freeradius responds in json format to the request to authorize
From:       Alan DeKok <aland () deployingradius ! com>
Date:       2017-07-26 18:55:14
Message-ID: 8BCEA2C2-29F6-404F-B8C5-63E78794C48B () deployingradius ! com
[Download RAW message or body]

On Jul 26, 2017, at 2:46 PM, Fiorella De Luca via Freeradius-Users \
<freeradius-users@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?

  Yes.

  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.

> Example: 
> check the user exists, check password matches, check user has not exhausted their \
> allocated daily bandwidth.

  yes.

  Alan DeKok.


-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


[prev in list] [next in list] [prev in thread] [next in thread]