Skip navigation.

Configuring and Managing WebLogic SIP Server

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

Configuring P-Asserted-Identity Assertion

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:

 


Understanding Trusted Host Forwarding with P-Asserted-Identity

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

Forwarding Restrictions with P-Asserted-Identity and Privacy Headers


 

 


Overview Strict and Non-Strict P-Asserted-Identity Asserter Providers

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.

 


Configuring a P-Asserted-Identity Assertion Provider

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:

  1. Log in to the Administration Console for the WebLogic SIP Server domain you want to configure.
  2. In the left pane of the Console, expand the Security->Realms->myrealm->Providers->Authentication node.
  3. Select the Authentication node in the left pane.
  4. In the right pane of the Console, select one of the following options:
  5. See Overview Strict and Non-Strict P-Asserted-Identity Asserter Providers for more information.

  6. Enter a name for the new provider and click Create.
  7. Select the Details tab to display the new provider's configuration.
  8. Fill in the fields of the Details tab as follows:
  9. Click Apply.

 

Skip navigation bar  Back to Top Previous Next