Configuring and Managing WebLogic SIP Server
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
The following sections describe how the P-Asserted-Identity
and privacy
headers affect forwarding to trusted and non-trusted hosts, and how to configure a WebLogic SIP Server P-Asserted-Identity Asserter provider:
WebLogic SIP Server supports the P-Asserted-Identity
SIP header as described in RFC3325. To enable use of this header, you must configure one of two available P-Asserted Identity Assertion provider as described in Configuring a P-Asserted-Identity Assertion Provider.
When WebLogic SIP Server receives a message having the P-Asserted-Identity
header from a trusted host configured with the provider, it logs in the user specified in the header to determine group membership and other privileges.
The presence of a P-Asserted-Identity
header combined with the Privacy
header also determines whether WebLogic SIP Server forwards a given message to trusted and non-trusted hosts. Figure 11-1 summarizes the forwarding restrictions with P-Asserted-Identity
.
Figure 11-1 Forwarding Restrictions with P-Asserted-Identity and Privacy Headers
If the contents of a P-Asserted-Identity header are invalid, or if the header is received from a non-trusted host, then the security provider returns an "anonymous" user to the SIP Servlet container. If you configured the PAsserted Identity Strict Asserter provider, an exception is also thrown so that you can audit the substitution of the anonymous user. (If you configured the basic PAsserted Identity Asserter provider, no exception is thrown.)
With either provider, if the requested resource is protected, the SIP container then uses the authentication method defined in the auth-type
element in the Servlet's sip.xml
deployment descriptor to authorize the request. (For example, digest authentication may be used if the Servlet specifies the digest authentication method.)
If the requested resource is not protected, the anonymous user is simply passed to the SIP Servlet without authorization.
Follow these steps to configure a security provider used to support the P-Asserted-Identity
header. Note that one of two providers can be selected, as described in Overview Strict and Non-Strict P-Asserted-Identity Asserter Providers:
P-Asserted-Identity
header is invalid or is received from a non-trusted host and an anonymous user is substituted.P-Asserted-Identity
header is invalid or is received from a non-trusted host and an anonymous user is substituted.See Overview Strict and Non-Strict P-Asserted-Identity Asserter Providers for more information.
sipserver.xml
file (sip-security
.)P-Asserted-Identity
header to user names in the default security realm. Or, leave this field blank to use the default user name mapper. See Configuring a User Name Mapper in the WebLogic Server 8.1 Documentation for more information.
![]() ![]() |
![]() |
![]() |