Hello Elvind -
Yes this is fairly simple to do with multiple AuthBy clauses - in this case
with a trailing AuthBy FILE to set the required reply attributes.
Depending on how many groups you need, it may be preferable to have a group
attribute in each user record rather than use memberOf.
In
Hugh Irvine wrote:
Yes this is fairly simple to do with multiple AuthBy clauses - in this
case with a trailing AuthBy FILE to set the required reply attributes.
My plan is to avoid the entire AuthBy FILE, if I can, so whoever is
provisioning these users won't have to also edit a file, adding
On 09/24/2013 05:47 PM, Tim Jones wrote:
The debug output from the server shows the database being updated and
returning ACCEPT, but then never sends out the Access-Accept response
packet back to the NAS.
Hello Tim,
since you run this from ReplyHook returning from the Hook will not wind
back
Hello Elvind -
Yes your approach will also work - I misunderstood your original question and
thought you wanted to retain the AuthBy FILE component.
The AuthBy FILE part would only be to hold the group reply attributes, which
as you say can also be done with AddToReply in the simple case.
Radiator 4.12.1 patches now have changes affecting handling unknown
attributes and proxying them.
Unknown attributes are now always accepted. A single warning, not error,
is logged for each unknown attribute per sender. This will reduce the
number of log messages but allows to keep an eye on
