On Oct 16, 2025, at 4:01 AM, bryan xiang <bryanxiang82@gmail.com> wrote:
I am testing customized rlm_jradius work with rlm_tacacs, the work flow is auth request go to rlm_jradius module firstly, if return the user should go to tacacs, then request will go to rlm_tacacs.
OK. The one thing to note is that there is no rlm_jradius in v4. So if you've ported it from v3, you'll need to do that correctly. Porting it is not just fixing the APIs. The entire attribute structure has changed.
The question is I want to get some reply attributes from jradius and decide if we should go to the subrequest for tacacs module, I tried some methods, but the reply is null.
Then fix the rlm_jradius module to work correctly for v4. You're asking us to help debug an issue with custom code. And, where you're not sharing the custom code. That makes it nearly impossible to help you. Given how jradius works, we're not going to support it in v4. I would suggest just debugging the code. Print out the various lists. There are many APIs to do that. See src/lib/util/pair.h for helper functions. Then, work through how the module works. There are many examples of adding reply attributes to the server. There are many modules which do exactly that. The source code is available, and you can look at it to see what they are doing. Alan DeKok.