Custom Properties The following custom property is available:

11-28 Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite config.putjavax.xml.ws.BindingProvider.USERNAME_PROPERTY, test.user1; PresenceConsumerClient presenceClient = new PresenceConsumerClientconfig;

11.5.4 Keystore Configuration

In order to use the recommended WS-Security policy, you must configure a keystore containing the public and private key information required by OWSM. Refer to Configuring the Credential Store Using WLST in Oracle Fusion Middleware Securing WebLogic Web Services for Oracle WebLogic Server for information on how to configure the keystore and corresponding credential store entries. ■ If both your web service client and UMS server are in the same domain, then they share a keystore and credential store. ■ If your web service client and UMS server are in different domains, then you must import the UMS public key into your client domains keystore, and must import your client domains public key into the UMS keystore.

11.5.5 Client Aliases

When using certain WS-Security policies such as the SAML policy recommended here, the client must use the servers public key to encrypt the web service request. However, there is generally only one keystore configured per domain. Therefore, if you have a domain in which there are web service clients that communicate with web services in multiple other domains, then you may need to override the default keystore entry used by OWSM. For example, if you have a domain in which application A is a web service client to a UMS web service, and application B is a web service client to a web service in another domain, then As requests must be encrypted using the public key of the UMS domain, and Bs requests must be encrypted using the public key of the other domain. You can accomplish this goal by overriding the keystore alias used by OWSM for each request: ■ Import for example the UMS public key with alias ums_public_key, and the other public key with alias other_public_key. ■ When creating an UMS web service client, specify the recipient keystore alias parameter, setting the key to oracle.wsm.security.util.SecurityConstants.Config.KEYSTORE_ RECIPIENT_ALIAS_PROPERTY and the value to ums_public_key as shown in Example 11–2 . Example 11–2 Client Aliases import oracle.sdp.parlayx.multimedia_messaging.send.SendMessageClient ... MapString, Object config = new HashMapString, Object; config.putjavax.xml.ws.BindingProvider.ENDPOINT_ADDRESS_PROPERTY, ums_url; config.putoracle.sdp.parlayx.ParlayXConstants.POLICIES, new String[] {oraclewss11_saml_token_with_message_protection_client_policy}; config.putjavax.xml.ws.BindingProvider.USERNAME_PROPERTY, test.user1; config.putoracle.wsm.security.util.SecurityConstants.Config.KEYSTORE_RECIPIENT_ ALIAS_PROPERTY, ums_public_key SendMessageClient sendClient = new SendMessageClientconfig;