You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unexpected behaviour (obvious or verified by project member)
How can the issue be reproduced?
In rlm_perl, the value of an attribute can be set to an array. This can used to give (for example) a RADIUS reply with multiple attributes having the same name and different values.
In rlm_python3, this does not work. If an attribute is value set to an array or tuple, then the attribute is simply not set at all.
What type of defect/bug is this?
Unexpected behaviour (obvious or verified by project member)
How can the issue be reproduced?
In rlm_perl, the value of an attribute can be set to an array. This can used to give (for example) a RADIUS reply with multiple attributes having the same name and different values.
In rlm_python3, this does not work. If an attribute is value set to an array or tuple, then the attribute is simply not set at all.
For example:
Would be expected to set reply attributes:
Instead, it does not set anything.
Log output from the FreeRADIUS daemon
Relevant log output from client utilities
No response
Backtrace from LLDB or GDB
No response
The text was updated successfully, but these errors were encountered: