How to copy all EAP Request Attributes to internal server?
hello, An external request must be used on the internal server to transfer Attributes from the internal server to the REST module. Until now, we copied Attributes one by one. example) &Calling-Station-Id = &outer.request:Calling-Station-Id &Called-Station-Id = &outer.request:Called-Station-Id No problem. But now we are in a situation where we have to use all Attributes. So what I tried &request = &outer.request All Attributes were copied, but authentication could not be completed because Attributes that should not have been copied were also copied. (EAP session-related properties) Other than the method just mentioned, there are only two methods that I know of. 1. As in the example, specify all Attributes one by one. 2. Change the copy_request_to_tunnel option of the EAP module to “yes”. Option 1 is the least desirable method. If it becomes necessary to add an attribute, a restart of FreeRADIUS is required. 2. It's the simplest method, but the documentation says "use it only for compatibility reasons." I got the "don't use it" feeling here. I don't know the exact reason, but it's probably for security reasons. Is there a better way you know? Or is there no problem if I just use copy_request_to_tunnel ?
On Apr 12, 2024, at 5:09 AM, 남혁준 <sawd1598@gmail.com> wrote:
An external request must be used on the internal server to transfer Attributes from the internal server to the REST module.
Until now, we copied Attributes one by one.
Why? There are many ways to get things done in FreeRADIUS, If it's very complicated to do something, then usually there's a simpler way.
2. It's the simplest method, but the documentation says "use it only for compatibility reasons."
I got the "don't use it" feeling here. I don't know the exact reason, but it's probably for security reasons.
No. It's because there are better ways to do things. But if it works and it's simple, it should be fine. Alan DeKok.
thank you. If you don't mind, could you give me an example of the "better way" you mentioned other than the "copy_request_to_tunnel" option? for example a := a b := b c := c ... I think you know of another method other than this cumbersome manual work. 2024년 4월 12일 (금) 오후 8:17, Alan DeKok <aland@deployingradius.com>님이 작성:
On Apr 12, 2024, at 5:09 AM, 남혁준 <sawd1598@gmail.com> wrote:
An external request must be used on the internal server to transfer Attributes from the internal server to the REST module.
Until now, we copied Attributes one by one.
Why? There are many ways to get things done in FreeRADIUS, If it's very complicated to do something, then usually there's a simpler way.
2. It's the simplest method, but the documentation says "use it only for compatibility reasons."
I got the "don't use it" feeling here. I don't know the exact reason, but it's probably for security reasons.
No.
It's because there are better ways to do things. But if it works and it's simple, it should be fine.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Apr 12, 2024, at 12:17 PM, 남혁준 <sawd1598@gmail.com> wrote:
If you don't mind, could you give me an example of the "better way" you mentioned other than the "copy_request_to_tunnel" option?
The better way is usually to describe the requirements. i.e. I want to get attributes A, B, and C into the REST API. The problem many people ask is instead about a solution. i.e. I tried to X and it didn't work, how do I do X? It's difficult to offer advice when we don't know the goal. If we do know the goal, we can often offer different ideas which maybe you didn't consider. Alan DeKok.
participants (2)
-
Alan DeKok -
남혁준