This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
custom_attributes [2014/08/22 19:50] 127.0.0.1 external edit |
custom_attributes [2016/10/11 00:17] admin |
||
---|---|---|---|
Line 14: | Line 14: | ||
===Processing Order=== | ===Processing Order=== | ||
- | If any attribute is specified more than once, the last occurance of that attribute will be used. You can specify which Attribute Value should be added first using the "Order" parameter. "Order" is a numeric integer value which specifies the order in which Custom attributes are processed. This order is shared between those Custom Attributes assigned to a Service and those assigned to a Customer. It means by using Order parameter, you can specify a certain Custom attribute assigned to a customer is processed before a Custom attribute assigned to a Service and therefore, the one from Service will override the one from Customer (if same RADIUS attribute is used). | + | You can specify which Attribute Value should be added first using the "Order" parameter. "Order" is a numeric integer value which specifies the order in which Custom attributes are processed. This order is shared between those Custom Attributes assigned to a Service and those assigned to a Customer. It means by using Order parameter, you can specify a certain Custom attribute assigned to a customer is processed before a Custom attribute assigned to a Service and therefore, the one from Service will appear before the one from Customer (if same RADIUS attribute is used). |
+ | |||
+ | Starting V 6.1.0, a negative value for Order parameter means this attribute will be overwriting any previously existing instance of this attribute in the response packet. Please note that a custom attribute overwrites **other custom attributes of the same type** only if Order of those other instances of the attribute is a smaller number. | ||
===Conditional Custom Attributes=== | ===Conditional Custom Attributes=== |