The documentation is quite lacking for the rest module, and contains features not yet published in version 3 (such as sub attributes). I did try many different options but none of them seemed to do the trick. When sending several instances of the same sub attribute in the json message only the last one was parsed by the rest module. Sending each sub attribute as a list of values works for parsing them all, but puts them one after the other in the radius packet and this is not what I need. I just want a way to send the same attribute several times and be able to control their order in the resulting radius packet. To summarize, I have a tlv with 2 sub attributes (sub1 and sub2). I want to send several instances of sub_1 and several instances of sub_2 in a json message to the rest module such that the resulting radius packet generated from the rest module will contain each instance of sub_attr_2 after its matching instance of sub_attr_1. I would appreciate a concrete json example :-) On Sun, Sep 10, 2017 at 9:58 PM Alan DeKok <aland@deployingradius.com> wrote:
On Sep 10, 2017, at 1:33 PM, Avner Elizarov <avnerelizarov@gmail.com> wrote:
What does the documentation say how the module works?
And does the rest module documentation describe how the json should be encoded?
And does the rest module documentation describe what it does with the json data?
I mean... come on. You can ask endless questions, or you can (a) try it and see what happens, and (b) read the documentation.
This shouldn't be complicated. Learn how to read documentation, and learn how to run tests.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html