Hi,
> Unfortunately that then causes the Chargeable-User-Identity to never make it into the final reply, even when I update the CUI code to use the outer reply instead of the inner. The Access-Challenge causes that to get swallowed.
>
> I've been going around in circles with this and tried everything. :-/
why fussing/dealing with the access-challenge? theres LOTS of those packets and dealing with such things in A-C packets
would be huge overhead.... and the RFCs state only certain attributes should be present in A-C packets
(attrs.access_challenge has a filter list....which is likely being used...and newer config has this:
if (handled && (Response-Packet-Type == Access-Challenge)) {
attr_filter.access_challenge.post-auth
handled # override the "updated" code from attr_filter
which will also be stripping out such things).
surely CUI only needs to be present in the Access-Accept packet? (for answer) and only in
Access-Request for the CUI request?
alan
|