Does SER support RFC3325? Does it understand headers like "Privacy", "P-Preferred-Identity" and "P-Asserted-Identity"? If so, how can we specify the Spec(T) to control SER's behavior? Thanks, -Ravi.
Gummadidala, Ravi writes:
Does SER support RFC3325? Does it understand headers like "Privacy", "P-Preferred-Identity" and "P-Asserted-Identity"? If so, how can we specify the Spec(T) to control SER's behavior?
ser can be "programmed" via ser.cfg file to add or drop any headers you like. if i remember correctly, currently there is no parsing of any p headers, but there is parsing of remote-party-id header, which can also be used to implement network asserted identity.
i guess you would need to add parsing of P-Preferred-Identity header and then modify proxy_authorize function so that it can authenticate request based on P-Preferred-Identity header instead of from header. maybe the most flexible solution would be to authenticate based on an AVP, which can before authentication loaded with uri from whatever header.
-- juha