The following sections describe how to configure WebLogic SIP Server to handle the X-3GPP-Asserted-Identity
header for HTTP authentication:
In order to function as an Application Server in an IMS network, WebLogic SIP Server supports handling the X-3GPP-Asserted-Identity
header as specified in
3GPP TS 33.222 Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS). WebLogic SIP Server provides this support via a configured security provider, X3gppAssertedIdentityAsserter
or X3gppAssertedIdentityStrictAsserter
. The providers use the same authentication process, but the "strict" assertion provider also throws an exception when the header is received from a non-trusted host (which enables you to audit asserted identity requests from non-trusted hosts).
The X-3GPP-Asserted-Identity
header functions for HTTP requests in the same manner that the P-Asserted-Identity
header functions for SIP requests. When the container receives an incoming HTTP requesting having a X-3GPP-Asserted-Identity
header, it first verifies that the request was received from a trusted host. If the host was trusted, the container asserts the user's identity using the information in the header, authenticates the user, and logs the user in if that user is authorized to access the requested resource. (If a request comes from a non-trusted host, the container simply ignores the header.)
The X-3GPP-Asserted-Identity
header may contain multiple names in a list (for example, user1@bea.com, user2@bea.com). When configured with the default user name mapper class, the WebLogic SIP Server providers remove the domain portion of the addresses (@bea.com
) and use the remainder as the user name. The default user name mapper always chooses the first username in the list and uses it for asserting the identity. This behavior can be changed by creating and configuring a custom user name mapper class. For example, if you must support overlapping usernames from different names (for example, sipuser@bea.com
and sipuser@cea.com
), a custom user-name mapper might process the header contents into a unique username (for example, sipsuser_b
and sipuser_c
). Using a custom user name mapper also enables you to support WebLogic user names that contain an "@" character, such as @bea.com
.
In order for SIP Servlets to support authentication with the X-3GPP-Asserted-Identity
header, the auth-method
element must be set to CLIENT-CERT
in the web.xml
deployment descriptor. See web.xml Deployment Descriptor Elements in the WebLogic Server 9.2 Documentation for more information.
Follow these steps to configure a security provider used to support the X-3GPP-Asserted-Identity
header in HTTP requests. Note that one of two providers can be selected, as described in the Overview:
See Overview for more information.
sipserver.xml
file (see
sip-security in Configuring and Managing WebLogic SIP Server.) You can enter a list of IP addresses or DNS names, and wildcards are supported.X-3GPP-Asserted-Identity
header to user names in the default security realm. A custom user name mapper is generally used if user names are received from two or more different domains. In this case additional logic may be required to map user names received from each domain. A custom user name mapper class is required if you want to map usernames to WebLogic usernames, or if you want to logically process multiple usernames specified in the X-3GPP-Asserted-Identity
header (rather than using only the first username). See
Configuring a Role Mapping Provider in the WebLogic Server 9.2 Documentation for more information.Alternately, leave this field blank to use the default user name mapper. The default mapper simply discards the domain name and takes the first resulting user name to assert the identity. For example, the default user name mapper takes the following header:
X-3GPP-Asserted-Identity: "user1@bea.com", "user2@bea.com"