Known Issues When P-Asserted-Identity Header Is Used With Privacy Header
(Doc ID 1086893.1)
Last updated on NOVEMBER 28, 2019
Applies to:Oracle Communications Converged Application Server - Version 4.0.0 to 5.0.0 [Release 4.0.0 to 5.0]
Information in this document applies to any platform.
What does the header look like?
P-Asserted-Identity + Privacy: id - RFC 3325
Privacy - RFC 3323
- When using an Application Router and configuring either trusted authentication hosts in sipserver.xml or an PAI Identity Asserter security provider in config.xml the P-Asserted-Identity: header is correctly kept.
- But when 'Privacy: id' is present as well, the P-Asserted-Identity: header is removed even if the sending or receiving host had been configured as a trusted host.
- It works well to configure a SIP application to use a PAI Identity Asserter security provider for evaluating the P-Asserted-Identity: header.
- But if this message contains a 'Privacy: id' header as well a 403 Forbidden error is returned even if the user inside the P-Asserted-Identity: header is known and the IP of the sending host is trusted. This can only be worked around by setting trusted authentication hosts in sipserver.xml to not call the PAI Identity Asserter security provider for all messages coming from such a host and containing a P-Asserted-Identity: header.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document