On 22.11.23 07:48, James Fan wrote:
Sorry, there is a mistake in the question. It should be:
Hmm. You do know that there are lot of more "mistakes" in your question that just that. Starting with the simple things like which version you are running or what exactly you are doing. Alan almost each time points out to the welcome message of this list and what's needed. Guessing from the lack of information you have provided, your issue seems to be in the use of the operating in your reply. It's unlang. You have used the operator to replace a value if there is already one. You want to use the operator which sets the value only if it's not already there. I think that should do it. But again, I am only guessing about what you are doing... Cheers, Gerald
Can we re-order the authorization queries by any configuration to make a higher priority for the user reply in the same attribute? Thanks.
On Wed, Nov 22, 2023 at 1:57 PM James Fan <polysorb@gmail.com> wrote:
We have a case that needs to prioritize the group reply attributes more than the user reply attributes in the same attribute. However, I found a fixed order for the authorization queries in the source code as below. radcheck -> radreply -> radgroupcheck -> radgroupreply If I change the orders in queries.conf, the query order is not changed while authorizing. So I wonder if we can re-order the authorization queries by any configuration to make higher priority for the group reply? Thanks.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html