How freeradius responds in json format to the request to authorize
Hello! I am a new Freeradius user. I'm participating in the Google Summer Code and I'm working on an OpenWISP project regarding the creation of a freeradius web interface. This app Django-freeradius will be a web interface to a manage freeradius database using a Django Rest framework . I I installed FreeRADIUS Version 3.0.12 on Ubuntu. I am using rlm_rest So I can configure freeradius to delegate some or all of its operations (authorization, authentication, accounting, mail order) to a REST API. But I can not understand how freeradius responds in json format to the request to authorize . I tried to accept the user with Auth-Type: = Accept And for the user to refuse: Auth-Type: = Reject but it does not work. If anyone could give me an explanation I'll be more than happy. Thank you!
On Jul 23, 2017, at 9:25 AM, Fiorella De Luca via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Hello! I am a new Freeradius user. I'm participating in the Google Summer Code and I'm working on an OpenWISP project regarding the creation of a freeradius web interface. This app Django-freeradius will be a web interface to a manage freeradius database using a Django Rest framework . I I installed FreeRADIUS Version 3.0.12 on Ubuntu. I am using rlm_rest So I can configure freeradius to delegate some or all of its operations (authorization, authentication, accounting, mail order) to a REST API.
OK...
But I can not understand how freeradius responds in json format to the request to authorize .
I'm not sure what that means...
I tried to accept the user with Auth-Type: = Accept And for the user to refuse: Auth-Type: = Reject but it does not work. If anyone could give me an explanation I'll be more than happy. Thank you!
Perhaps you could explain what you're trying to do. Explain in detail what you configured, what happened, and what you expected to happen. Alan DeKok.
On 23 Jul 2017, at 09:25, Fiorella De Luca via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Hello! I am a new Freeradius user. I'm participating in the Google Summer Code and I'm working on an OpenWISP project regarding the creation of a freeradius web interface. This app Django-freeradius will be a web interface to a manage freeradius database using a Django Rest framework .
That’s a good choice. We had a project to do that a while back, it just didn’t end up progressing far. I think the approach of using the Rest interface instead SQL is good. The SQL format is too limiting.
I installed FreeRADIUS Version 3.0.12 on Ubuntu. I am using rlm_rest So I can configure freeradius to delegate some or all of its operations (authorization, authentication, accounting, mail order)
Not sure what “mail order” is, but sure.
to a REST API. But I can not understand how freeradius responds in json format to the request to authorize . I tried to accept the user with Auth-Type: = Accept And for the user to refuse: Auth-Type: = Reject but it does not work. If anyone could give me an explanation I'll be more than happy. Thank you!
The request/response format is documented here: https://github.com/FreeRADIUS/freeradius-server/blob/v4.0.x/raddb/mods-avail... If you want response attributes to go into different lists, then you can qualify the attribute name with a list name. For your example of Auth-Type the JSON for ‘Accept’ would be: { “control:Auth-Type”:”Accept" } and for reject: { “control:Auth-Type”:”Reject" } Let me know if this doesn’t work. I’m fairly sure I added list qualifier extraction to the rim_rest module. If I didn’t it’s a simple fix. -Arran
participants (3)
-
Alan DeKok -
Arran Cudbard-Bell -
Fiorella De Luca