%Z variable or otherwise
Hello, There used to be a %Z variable which held the whole request in FR 2 and older. I understand that it’s gone in FR 3. Is there a way to get the same behaviour in 3.xx with another variable or some other unlang way? I used to send it to a database (with the sql post-auth query) indexed by username / calling station-id so I could look up the exact request after the fact and see all attributes sent by the NAS. ‘%Z’ allowed me to insert it in the database without having to know in advance what attributes would be sent. Thank you for your help, -- Louis Munro lmunro@inverse.ca :: www.inverse.ca +1.514.447.4918 x125 :: +1 (866) 353-6153 x125 Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)
On Feb 2, 2016, at 10:02 AM, Louis Munro <lmunro@inverse.ca> wrote:
Hello,
There used to be a %Z variable which held the whole request in FR 2 and older. I understand that it’s gone in FR 3.
Is there a way to get the same behaviour in 3.xx with another variable or some other unlang way?
I used to send it to a database (with the sql post-auth query) indexed by username / calling station-id so I could look up the exact request after the fact and see all attributes sent by the NAS. ‘%Z’ allowed me to insert it in the database without having to know in advance what attributes would be sent.
Thank you for your help,
%{pairs:<attribute reference>} e.g. %{pairs:&request:[*]} Would get you the request list. -Arran
On Feb 2, 2016, at 10:20 , Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
%{pairs:<attribute reference>}
e.g.
%{pairs:&request:[*]}
Would get you the request list.
Thank you. That is indeed a much cleaner way of doing it. Regards, -- Louis Munro lmunro@inverse.ca :: www.inverse.ca +1.514.447.4918 x125 :: +1 (866) 353-6153 x125 Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)
participants (2)
-
Arran Cudbard-Bell -
Louis Munro