Click Browse, and navigate to ORACLE_

Configuring Oracle User Messaging Service 11-27 ■ oraclewss11_saml_token_with_message_protection_service_ policy client-side

11.5.1 Web Service Security on Notification

The different Web services include corresponding notification Web services MessageNotification, PresenceNotification that run on the client side and receive notifications message delivery status, message receipt, presence status change when the appropriate event occurs. This implementation does not provide for the use of Web Service security WS-Security by default during notification of the clients. That is, the server assumes that the notification Web services running on the client side do not use WS-Security, and makes no attempt to authenticate itself when sending notifications. If you enable WS-Security on the client side, the notification from the server will fail because the notification SOAP request will be missing the required headers.

11.5.2 Enabling UMS Service Security

To enable a policy for an UMS web service, follow the steps in Configuring Oracle WSM Security Policies in Administration Console in Oracle Fusion Middleware Securing WebLogic Web Services for Oracle WebLogic Server, selecting policy oraclewss11_ saml_token_with_message_protection_service_policy. This configuration must be repeated for each service that you wish to secure.

11.5.3 Enabling Client Security

Web service client security must be enabled programmatically. When using the client libraries described in Parlay X Messaging Client API and Client Proxy Packages in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite, WS-Security policy configuration is provided when a client object is constructed. The client constructors take an argument of type MapString, Object. In general when using SAML authentication, the keyvalue pairs Table 11–25 should be added to the configuration map in addition to other required properties such as the endpoint address. Example 11–1 Web Service Client Security import oracle.sdp.parlayx.presence.consumer.PresenceConsumerClient; ... 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}; Table 11–25 Client security keys Key Type Typical Value oracle.sdp.parlayx.ParlayXConstants.POLI CIES String[] oraclewss11_saml_ token_with_message_ protection_client_ policy javax.xml.ws.BindingProvider.USERNAME_ PROPERTY String valid username oracle.wsm.security.util.SecurityConstan ts.Config.KEYSTORE_RECIPIENT_ALIAS_ PROPERTY String optional keystore alias for target service. See Client Aliases .