Follow these steps to Attach and Configure the WebLogic Web Service Policy:

1. Create a WebLogic web service.

   For more information, see "Roadmap for Implementing WebLogic (Java EE) Web Services" in Understanding Web Services

2. Attach the following policies:

   1. Wssp1.2-2007-Wss1.1-UsernameToken-Plain-EncryptedKey-Basic128.xml

   2. Wssp1.2-2007-SignBody.xml

   3. Wssp1.2-2007-EncryptBody.xml

      For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Configure identity and trust stores.

   For more information, see "Configure identity and trust" in Oracle WebLogic Server Administration Console Online Help

4. Configure message-level security.

   Note:

   You only need to configure the Confidentiality Key for a WS-Security 1.1 policy.

   For more information, see:

   • "Configuring Message-Level Security" in Securing WebLogic Web Services for Oracle WebLogic Server

   • "Create a Web Service security configuration" in Oracle WebLogic Server Administration Console Online Help

5. Deploy the web service.

   For more information, see "Install a Web Service" in Oracle WebLogic Server Administration Console Online Help

Follow these steps to attach and Configure the OWSM Client Policy:

1. Create a client proxy for the web service created earlier using clientgen or some other mechanism.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service client: oracle/wss11_username_token_with_message_protection_client_policy.

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

3. Configure the policy.

   For more information, see "oracle/wss11_username_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

4. Specify keystore.recipient.alias in the client configuration.

   For more information, see "oracle/wss11_username_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

5. Ensure that the keystore.recipient.alias keys specified for the client exist as trusted certificate entry in the trust store configured for the web service.

   For more information, see "oracle/wss11_username_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

6. Provide a valid username and password as part of the configuration.

   For more information, see "oracle/wss11_username_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

7. Invoke the web service method from the client.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

Follow these steps to attach and Configure the OWSM Policy:

1. Create and deploy a web service.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service:

   1. oracle/wss11_username_token_with_message_protection_service_policy.

      For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

Follow these steps to attach and Configure the WebLogic Web Service Client Policy:

1. Create a client proxy for the web service created using clientgen.

   For more information, see "Using the clientgen Ant Task to Generate Client Artifacts" in Developing JAX-WS Web Services for Oracle WebLogic Server

2. Attach the following policies:

   1. Wssp1.2-2007-Wss1.1-UsernameToken-Plain-EncryptedKey-Basic128.xml

   2. Wssp1.2-2007-SignBody.xml

   3. Wssp1.2-2007-EncryptBody.xml

      For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Provide the configuration for the server (encryption key) in the client.

   Note:

   Ensure that the encryption key specified is in accordance with the encryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server

4. Invoke the web service method from the client.

   For more information, see "Writing the Java Client Application Code to Invoke a Web Service" in Developing JAX-WS Web Services for Oracle WebLogic Server

Follow these steps to attach and Configure the WebLogic Web Service Policy, perform the following steps:

1. Create a WebLogic web service.

   For more information, see "Roadmap for Implementing WebLogic (Java EE) Web Services" in Understanding Web Services.

2. Use the @MTOM annotation in the web service.

   For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

Follow these steps to attach and configure the OWSM Client Policy:

1. Configure the client proxy for the web service using clientgen or some other mechanism.

2. If you did not use the @MTOM annotation in the web services, attach wsmtom_policy from the Management tab.

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

Follow these steps to attach and configure the OWSM Policy:

1. Configure the OWSM web service.

2. Attach wsmtom_policy from the Management tab.

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

Follow these steps to attach and configure the WebLogic Web Service Client Policy:

1. Create a client proxy for the web service created using clientgen.

2. If you did not attach the wsmtom_policy, use the @MTOM annotation in the web service client.

Follow these steps to attach and configure the WebLogic Web Service Policy:

1. Create a WebLogic web service.

   For more information, see "Roadmap for Implementing WebLogic (Java EE) Web Services" in Understanding Web Services

2. Attach the following policies:

   1. Wssp1.2-2007-SignBody.xml

   2. Wssp1.2-wss10_username_token_with_message_protection_owsm_policy.xml

   3. Wssp1.2-2007-EncryptBody.xml

      For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Configure identity and trust stores.

   For more information, see "Configure identity and trust" in Oracle WebLogic Server Administration Console Online Help.

4. Configure message-level security.

   For more information, see:

   • "Configuring Message-Level Security" in Securing WebLogic Web Services for Oracle WebLogic Server

   • "Create a Web Service security configuration" in Oracle WebLogic Server Administration Console Online Help

5. Deploy the web service.

   For more information, see Deploy a web service in Deploying Applications to Oracle WebLogic Server.

Follow these steps to attach and configure the OWSM Client Policy:

1. Create a client proxy to the web service created using clientgen or some other mechanism.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service client:

   1. oracle/wss10_username_token_with_message_protection_client_policy.

      For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

3. Configure the policy.

   For more information, see "oracle/wss10_username_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

   Note:

   Ensure that you use different keys for client (sign and decrypt key) and keystore recipient alias (server public key used for encryption). Ensure that the recipient alias is in accordance with the keys defined in the web service policy security configuration.

4. Ensure that the signing and encryption keys specified for the client exist as trusted certificate entries in the trust store configured for the web service.

5. Provide a valid username and password as part of the configuration.

6. Invoke the web service method from the client.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

To attach and configure the OWSM Policy, perform the following steps:

1. Create a web service.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service:

   1. oracle/wss10_username_token_with_message_protection_service_policy.

      For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

Follow these steps to attach and configure the WebLogic Web Service Client Policy:

1. Create a client proxy for the web service created using clientgen.

   For more information, see "Using the clientgen Ant Task to Generate Client Artifacts" in Developing JAX-WS Web Services for Oracle WebLogic Server

2. Attach the following policies:

   1. Wssp1.2-wss10_username_token_with_message_protection_owsm_policy.xml

   2. Wssp1.2-2007-SignBody.xml

   3. Wssp1.2-2007-EncryptBody.xml

      For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Configure the client for server (encryption key) and client certificates.

   Note:

   Ensure that the encryption key specified is in accordance with the encryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server

4. Invoke the web service method from the client.

   For more information, see "Writing the Java Client Application Code to Invoke a Web Service" in Developing JAX-WS Web Services for Oracle WebLogic Server

Follow these steps to attach and configure the WebLogic Web Service Policy:

1. Create a WebLogic web service.

   For more information, see "Roadmap for Implementing WebLogic (Java EE) Web Services" in Understanding Web Services

2. Attach the following policies:

   • Wssp1.2-2007-Saml2.0-SenderVouches-Wss1.1.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

   For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Configure the keystore properties for message signing and encryption. The configuration should be in accordance with the keystore used on the server side. Create the trust store out of the keystore by exporting both keys, and trust both of them while importing into trust store. Configure identity and trust stores.

   For more information, see "Configure identity and trust" in Oracle WebLogic Server Administration Console Online Help.

4. Configure message-level security.

   For more information, see

   • "Configuring Message-Level Security" in Securing WebLogic Web Services for Oracle WebLogic Server

   • "Create a Web Service security configuration" in Oracle WebLogic Server Administration Console Online Help

5. Attach new configuration using the annotation:

   @WssConfiguration(value="<my_security_configuration>") where <my_security_configuration> is the name of the Web Security Configuration created in previous step. 

   For more information, see "Configuring Message-Level Security" in Securing WebLogic Web Services for Oracle WebLogic Server

6. Deploy the web service.

   For more information, see Deploy a web service in Deploying Applications to Oracle WebLogic Server.

7. Create a SAML Identity Asserter.

   In the WebLogic Server Remote Console, navigate to Security Realms > RealmName > Providers > Credential Mapping page and create a New Credential Mapping Provider of type SAML2IdentityAsserter.

   For more information, see "Configure Authentication and Identity Assertion providers" in Oracle WebLogic Server Administration Console Online Help

8. Restart WebLogic Server.

   For more information, see "Start and stop servers" in the Oracle WebLogic Server Administration Console Online Help.

9. To add the identity provider to the identity asserter created in Step 7, perform the following steps:

   1. Select the identity asserter created in Step 7 in the WebLogic Remote Console.

   2. Create a new identity provider partner, select New, and then select New Webservice Identity Provider Partner.

   3. Provide a name, and select Finish.

10. Configure the identity provider as follows:

    1. Select the identity provide partner created in Step 9.

    2. Select the Enabled check box.

    3. Provide the Audience URI. For example:

       target:*:/saml20WLSWS-Project1-context-root/Class1Port

    4. Set Issuer URI to www.oracle.com.

    5. Set Target URL to <url_used_to_access_Web_service>.

    6. Set Profile to WSS/Sender-Vouches.

Follow these steps to attach and configure the OWSM Client Policy:

1. Generate a client using JDeveloper for the web service created earlier. Create a Web project and then select New, and create a client proxy using the WSDL.

   For more information, see

   • "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

   • "Developing and Securing Web Services" in Developing Applications with Oracle JDeveloper.

2. Add a servlet in the above project.

3. Attach the following policy to the web service client: oracle/wss11_saml20_token_with_message_protection_client_policy.

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

4. Specify keystore.recipient.alias in the client configuration.

   Note:

   Ensure that keystore.recipient.alias is same as the decryption key specified for the web service.

   For more information, see "oracle/wss11_saml20_token_with_message_protection_cient_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

5. Ensure that the keystore.recipient.alias keys specified for the client exist as trusted certificate entry in the trust store configured for the web service.

   For more information, see "oracle/wss11_saml20_token_with_message_protection_cient_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

6. In JDeveloper, secure web project with Form-based authentication using the Configure ADF Security Wizard.

   For more information, see Developing Applications with Oracle JDeveloper

7. Invoke the Web application client.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

Follow these steps to attach and configure the OWSM Policy:

1. Create a web service.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service:

   oracle/wss11_saml20_token_with_message_protection_service_policy.

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

Follow these steps to attach and configure the WebLogic Web Service Client:

1. Create a Java EE client for the deployed web service using JDeveloper. Create a Web project and create a proxy using WSDL proxy.

   For more information, see "Creating JAX-WS Web Services and Clients" in Developing Applications with Oracle JDeveloper

2. Attach the following policies:

   • Wssp1.2-2007-Saml2.0-SenderVouches-Wss1.1.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

     Note:

     Extract weblogic.jar to a folder and provide the absolute path to the above policies files.

     For more information, see "Attaching Policies" in Developing Applications with Oracle JDeveloper

3. Add servlet to above web project.

4. Configure the client for server (encryption key) and client certificates.

   Note:

   Ensure that the encryption key specified is in accordance with the decryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server

5. Secure the Web application client using BASIC Authentication.

   For more information, see "Developing BASIC Authentication Web Applications" in Developing Applications with the WebLogic Security Service

6. Deploy the Java EE Web application client.

   For more information, see "Deploying Web Services Applications" in Administering Web Services

7. Configure a SAML credential mapping provider.

   • In the Oracle WebLogic Server Remote Console, navigate to Security Realms > RealmName > Providers > Credential Mapping page and create a New Credential Mapping Provider of type SAML2CredentialMapper.

8. Select the new provider, click on Provider Specific, and configure it as follows:

   1. Set Issuer URI to www.oracle.com.

   2. Set Name Qualifier to www.oracle.com.

   For more information, see "Configure Credential Mapping Providers" in Oracle WebLogic Server Administration Console Online Help

9. Restart WebLogic Server.

   For more information, see "Start and stop servers" in the Oracle WebLogic Server Administration Console Online Help.

10. To create a new service provider partner, perform the following steps:

    1. Select the credential mapper created in Step 7 in the WebLogic Remote Console, and then select the Management tab.

    2. Select New, and then select New Webservice Service Provider Partner.

    3. Provide a name, and select Finish.

11. Configure the service provider partner as follows:

    1. Select the service provide partner created in Step 10.

    2. Select the Enabled check box.

    3. Provide the Audience URI.

    4. Set Issuer URI to www.oracle.com.

    5. Set Target URL to <url_used_to_access_Web_service>.

    6. Set Profile to WSS/Sender-Vouches.

12. Invoke the Web application client.

    • Enter the credentials of the user whose identity is to be propagated using SAML token.

      For more information, see "Writing the Java Client Application Code to Invoke a Web Service" in Developing JAX-WS Web Services for Oracle WebLogic Server

Follow these steps to attach and configure the WebLogic Web Service Policy:

1. Create a WebLogic web service.

   For more information, see "Roadmap for Implementing WebLogic (Java EE) Web Services" in Understanding Web Services

2. Attach the following policies:

   • Wssp1.2-wss11_saml_token_with_message_protection_owsm_policy.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

     For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server.

3. Configure identity and trust stores.

   For more information, see "Configure identity and trust" in Oracle WebLogic Server Administration Console Online Help

4. Configure message-level security.

   Note:

   Since this is a WS-Security 1.1 policy, you need to configure Confidentiality Key only.

   For more information, see

   • "Configure Message-Level Security" in Securing WebLogic Web Services for Oracle WebLogic Server

   • "Create a Web Service security configuration" in Oracle WebLogic Server Administration Console Online Help.

5. Deploy the web service.

   For more information, see Deploy a web service in Deploying Applications to Oracle WebLogic Server.

6. Create a SAMLIdentityAsserterV2 authentication provider.

   • In the WebLogic Server Remote Console, navigate to Security Realms > RealmName > Providers > Credential Mapping page and create a New Credential Mapping Provider of type SAMLCredentialMapperV2.

     For more information, see "Configuring Authentication and Identity Assertion providers" in Oracle WebLogic Server Administration Console Online Help

7. Restart WebLogic Server.

   For more information, see "Start and stop servers" in the Oracle WebLogic Server Administration Console Online Help.

8. Select the authentication provider created in step 5.

9. Create a SAML asserting party.

   • Set Profile to WSS/Sender-Vouches.

   For more information, see "Create a SAML 1.1 Asserting Party" in Oracle WebLogic Server Administration Console Online Help

10. Configure the SAML asserting party as follows:

    1. Set Issuer URI to www.oracle.com.

    2. Set Target URL to <url_used_to_access_Web_service>.

       For more information, see "Create a SAML 1.1 Asserting Party" in Oracle WebLogic Server Administration Console Online Help

Follow these steps to attach and configure the OWSM Client Policy:

1. Create a client proxy to the web service created earlier using clientgen or some other mechanism.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service client:

   • oracle/wss11_saml_token_with_message_protection_client_policy.

     For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

3. Configure the policy, as described in oracle/wss11_saml_token_with_message_protection_client_policy.

   For more information, see "oracle/wss11_saml_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

4. Specify keystore.recipient.alias in the client configuration.

   Note:

   Ensure that keystore.recipient.alias is the same as the decryption key specified for the web service.

   For more information, see "oracle/wss11_saml_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

5. Ensure that the keystore.recipient.alias keys specified for the client exist as trusted certificate entry in the trust store configured for the web service.

   For more information, see "oracle/wss11_saml_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

6. Provide a valid username whose identity needs to be propagated using SAML token in the client configuration.

   For more information, see "oracle/wss11_saml_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

7. Invoke the Web application client.

   • Enter the credentials of the user whose identity is to be propagated using SAML token.

     For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

Follow these steps to attach and configure the OWSM Policy:

1. Create a web service.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service:

   • oracle/wss11_saml_token_with_message_protection_service_policy.

     For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

Follow these steps to attach and configure the WebLogic Web Service Client Policy:

1. Create a client proxy for the web service (above) using clientgen.

   For more information, see "Using the clientgen Ant Task to Generate Client Artifacts" in Developing JAX-WS Web Services for Oracle WebLogic Server

2. Attach the following policies:

   • Wssp1.2-wss11_saml_token_with_message_protection_owsm_policy.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

     For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Configure the client for server (encryption key) and client certificates.

   Note:

   Ensure that the encryption key specified is in accordance with the decryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server

4. Secure the Web application client using BASIC Authentication.

   For more information, see "Developing BASIC Authentication Web Applications" in Developing Applications with the WebLogic Security Service.

5. Deploy the web service client.

   For more information, see "Deploying Web Services Applications" in Administering Web Services

6. Configure a SAML credential mapping provider.

   • In the Oracle WebLogic Server Remote Console, navigate to Security Realms > RealmName > Providers > Credential Mapping page and create a New Credential Mapping Provider of type SAMLCredentialMapperV2.

7. Select the new provider, click on Provider Specific, and configure it as follows:

   1. Set Issuer URI to www.oracle.com.

   2. Set Name Qualifier to www.oracle.com.

      For more information, see "Configure Credential Mapping Providers" in Oracle WebLogic Server Administration Console Online Help

8. Restart WebLogic Server.

   For more information, see "Start and stop servers" in the Oracle WebLogic Server Administration Console Online Help.

9. Create a SAML relying party.

   • Set the Profile to WSS/Sender-Vouches.

     For more information, see "Create a SAML 1.1 Relying Party" and "Configure a SAML 1.1 Relying Party" in Oracle WebLogic Server Administration Console Online Help

10. Configure the SAML relying party.

    • Ensure the Target URL is set to the URL used for the client web service.

      For more information, see "Configure a SAML 1.1 Relying Party" in Oracle WebLogic Server Administration Console Online Help

11. Invoke the Web application client.

    • Enter the credentials of the user whose identity is to be propagated using SAML token.

      For more information, see "Writing the Java Client Application Code to Invoke a Web Service" in Developing JAX-WS Web Services for Oracle WebLogic Server

Follow these steps to attach and configure the WebLogic Web Service Policy:

1. Create a WebLogic web service, as described in SAML Token (Sender Vouches) with Message Protection (WS-Security 1.1) for Oracle WebLogic Server

   For more information, see "Roadmap for Implementing WebLogic (Java EE) Web Services" in Understanding Web Services

2. Use the @MTOM annotation in the web service in Step 2 of " Attaching and Configuring the WebLogic Web Service Policy".

   For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

Follow these steps to attach and configure the OWSM Client Policy:

1. Create a client proxy to the web service created earlier, as described in SAML Token (Sender Vouches) with Message Protection (WS-Security 1.1) for Oracle WebLogic Server

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach wsmtom_policy from the Management tab.

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

Follow these steps to attach and configure the OWSM Policy:

1. Create and deploy a web service.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service:

   • oracle/wss11_username_token_with_message_protection_service_policy.

     For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

Follow these steps to attach and configure the WebLogic Web Service Client Policy:

1. Create a client proxy for the web service created earlier using clientgen.

   For more information, see "Using the clientgen Ant Task to Generate Client Artifacts" in Developing JAX-WS Web Services for Oracle WebLogic Server

2. Attach the following policies:

   • Wssp1.2-2007-Wss1.1-UsernameToken-Plain-EncryptedKey-Basic128.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

   For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Provide the configuration for the server (encryption key) in the client.

   Note:

   Ensure that the encryption key specified is in accordance with the encryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server

4. Invoke the web service method from the client.

   For more information, see "Writing the Java Client Application Code to Invoke a Web Service" in Developing JAX-WS Web Services for Oracle WebLogic Server

Follow these steps to attach and configure the WebLogic Web Service Policy:

1. Create a WebLogic web service.

   For more information, see "Roadmap for Implementing WebLogic (Java EE) Web Services" in Understanding Web Services

2. Attach the following policies:

   • Wssp1.2-wss10_saml_token_with_message_protection_owsm_policy.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

3. Configure identity and trust stores.

   For more information, see "Configure identity and trust" in Oracle WebLogic Server Administration Console Online Help

4. Configure message-level security.

   For more information, see

   • "Configuring Message-Level Security" in Securing WebLogic Web Services for Oracle WebLogic Server

   • "Create a Web Service security configuration" in Oracle WebLogic Server Administration Console Online Help

5. Deploy the web service.

   For more information, see Deploy a web service in Deploying Applications to Oracle WebLogic Server.

6. Create a SAMLIdentityAsserterV2 authentication provider.

   • In the WebLogic Server Remote Console, navigate to Security Realms > RealmName > Providers > Credential Mapping page and create a New Credential Mapping Provider of type SAMLCredentialMapperV2.

     For more information, see "Configure Authentication and Identity Assertion providers" in Oracle WebLogic Server Administration Console Online Help

7. Restart WebLogic Server.

   For more information, see "Start and stop servers" in the Oracle WebLogic Server Administration Console Online Help.

8. Select the authentication provider created in step 5.

9. Create a SAML asserting party.

   • Set Profile to WSS/Sender-Vouches.

     For more information, see "Create a SAML 1.1 Asserting Party" in Oracle WebLogic Server Administration Console Online Help

10. Configure the SAML asserting party as follows (leave other values set to the defaults):

    1. Set Issuer URI to www.oracle.com.

    2. Set Target URL to <url_used_by_client>.

       For more information, see "Configure a SAML 1.1 Asserting Party" in Oracle WebLogic Server Administration Console Online Help

Follow these steps to attach and configure the OWSM Client Policy:

1. Create a client proxy to the web service created earlier using clientgen or some other mechanism.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service client:

   • oracle/wss10_saml_token_with_message_protection_client_policy.

     For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

3. Configure the policy.

   For more information, see "oracle/wss10_saml_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

4. Ensure that you use different keys for client (sign and decrypt key) and keystore recipient alias (server public key used for encryption). Ensure that the recipient alias is in accordance with the keys defined in the web service policy security configuration.

   For more information, see "oracle/wss10_saml_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

5. Ensure that the signing and encryption keys specified for the client exist as trusted certificate entries in the trust store configured for the web service.

   For more information, see "oracle/wss10_saml_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

6. Provide valid username whose identity needs to be propagated using SAML token in the client configuration.

   For more information, see "oracle/wss10_saml_token_with_message_protection_client_policy" in Securing Web Services and Managing Policies with Oracle Web Services Manager

7. Invoke the web service method.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

Follow these steps to attach and configure the OWSM Policy:

1. Create a web service.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service:

   • oracle/wss10_saml_token_with_message_protection_service_policy.

     For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

Follow these steps to attach and configure the WebLogic Web Service Client Policy:

1. Create a client proxy for the web service (above) using clientgen.

   For more information, see "Using the clientgen Ant Task to Generate Client Artifacts" in Developing JAX-WS Web Services for Oracle WebLogic Server

2. Attach the following policies:

   • Wssp1.2-wss10_saml_token_with_message_protection_owsm_policy.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

     For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Configure the client for server (encryption key) and client certificates.

   Note:

   Ensure that the encryption key specified is in accordance with the decryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server

4. Secure the Web application client using BASIC Authentication.

   For more information, see "Developing BASIC Authentication Web Applications" in Developing Applications with the WebLogic Security Service

5. Deploy the web service client.

   For more information, see "Deploying Web Services Applications" in Administering Web Services

6. Configure a SAML credential mapping provider.

   • In the WebLogic Server Remote Console, navigate to Security Realms > RealmName > Providers > Credential Mapping page and create a New Credential Mapping Provider of type SAMLCredentialMapperV2.

     For more information, see "Configure Credential Mapping Providers" in Oracle WebLogic Server Administration Console Online Help

7. Select the SAMLCredentialMapperV2, click on Provider Specific, and configure it as follows:

   1. Set Issuer URI to www.oracle.com.

   2. Set Name Qualifier to www.oracle.com.

8. Restart WebLogic Server.

   For more information, see "Start and stop servers" in the Oracle WebLogic Server Administration Console Online Help.

9. Create a SAML relying party. Set the profile to WSS/Sender-Vouches.

   For more information, see "Create a SAML 1.1 Relying Party" in Oracle WebLogic Server Administration Console Online Help

10. Configure the SAML relying party.

    Note:

    Ensure the target URL is set to the URL used for the client web service.

    For more information, see "Configure a SAML 1.1 Relying Party" in Oracle WebLogic Server Administration Console Online Help

11. Invoke the Web application client and enter the appropriate credentials.

    For more information, see "Writing the Java Client Application Code to Invoke a Web Service" in Developing JAX-WS Web Services for Oracle WebLogic Server

Follow these steps to attach and configure the WebLogic Web Service Policy:

1. Create a WebLogic web service.

   For more information, see "Roadmap for Implementing WebLogic (Java EE) Web Services" in Understanding Web Services

2. Attach the following policies:

   1. Wssp1.2-wss10_x509_token_with_message_protection_owsm_policy.xml

   2. Wssp1.2-2007-SignBody.xml

   3. Wssp1.2-2007-EncryptBody.xml

      For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Configure identity and trust stores.

   For more information, see "Configure identity and trust" in Oracle WebLogic Server Administration Console Online Help

4. Configure message-level security.

   For more information, see

   • "Configuring Message-Level Security" in Securing WebLogic Web Services for Oracle WebLogic Server

   • "Create a Web Service security configuration" in Oracle WebLogic Server Administration Console Online Help

5. Create and configure token handlers for X.509 and for username token. In WebLogic Remote Console, navigate to the Web Service Security page of the domain and create the token handlers as described below.

6. Create a token handle for username token and configure the following:

   1. Name: <name>

   2. Class name:

      weblogic.xml.crypto.wss.UsernameTokenHandler

   3. Token Type: ut

   4. Handling Order: 1

7. Create a token handler for X.509 and configure the following:

   1. Name: <name>

   2. Class name:

      weblogic.xml.crypto.wss.BinarySecurityTokenHandler

   3. Token Type: x509

   4. Handling Order: 0

8. For the X.509 token handler, add the following properties:

   1. Name: UserX509ForIdentity

   2. Value: true

   3. IsEncrypted: False

9. Configure a credential mapping provider. Create a PKICredentialMapper and configure it as follows (leave all other values set to the defaults):

   1. Keystore Provider: N/A

   2. Keystore Type: jks

   3. Keystore File Name: default_keystore.jks

   4. Keystore Pass Phrase: <password>

   5. Confirm Keystore Pass Phrase: <password>

10. Configure Authentication by Selecting the Authentication tab and configure as follows:

    1. Click DefaultIdentityAsserter and add X.509 to Chosen active types

    2. Click Provider Specific and configure the following:

       Default User Name Mapper Attribute Type: CN

       Active Types: X.509

       Use Default User Name Mapper: True

       For more information, see "Configure Authentication and Identity Assertion providers" in Oracle WebLogic Server Administration Console Online Help.

11. If the users are not added, add the Common Name (CN) user specified in the certificate.

    For more information, see "Create users" in Oracle WebLogic Server Administration Console Online Help

12. Restart Oracle WebLogic Server.

13. Deploy the web service.

    For more information, see "Install a Web Service" in Oracle WebLogic Server Administration Console Online Help

Follow these steps to attach and configure the OWSM Client Policy:

1. Create a client proxy to the web service created earlier using clientgen or some other mechanism.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the client:

   wss10_x509_token_with_message_protection_client_policy

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

3. Provide the configuration for the server (encryption key) in the client.

   Note:

   Ensure that the encryption key specified is in accordance with the encryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server

4. Invoke the web service method from the client.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

Follow these steps to attach and configure the OWSM Policy:

1. Create and deploy a web service application.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service:

   oracle/wss10_x509_token_with_message_protection_service_policy.

Follow these steps to attach and configure the WebLogic Web Service Client Policy:

1. Create a client proxy for the web service created earlier using clientgen.

   For more information, see "Using the clientgen Ant Task to Generate Client Artifacts" in Developing JAX-WS Web Services for Oracle WebLogic Server

2. Attach the following policies:

   • Wssp1.2-wss10_x509_token_with_message_protection_owsm_policy.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

     For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Provide the configuration for the server (encryption key) in the client.

   Note:

   Ensure that the encryption key specified is in accordance with the encryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server

4. Invoke the web service method from the client.

   For more information, see "Writing the Java Client Application Code to Invoke a Web Service" in Developing JAX-WS Web Services for Oracle WebLogic Server

Follow these steps to attach and configure the WebLogic Web Service Policy:

1. Create a WebLogic web service.

   For more information, see "Roadmap for Implementing WebLogic (Java EE) Web Services" in Understanding Web Services

2. Attach the following policies:

   • Wssp1.2-wss11_x509_token_with_message_protection_owsm_policy.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

     For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Configure identity and trust stores.

   For more information, see "Configure identity and trust" in Oracle WebLogic Server Administration Console Online Help

4. Configure message-level security.

   For more information, see

   • "Configuring Message-Level Security" in Securing WebLogic Web Services for Oracle WebLogic Server

   • "Create a Web Service security configuration" in Oracle WebLogic Server Administration Console Online Help

5. Create and configure token handlers for X.509 and for username token. In WebLogic Remote Console, navigate to the Web Service Security page of the domain and create the token handlers as described below.

6. Create a token handle for username token and configure the following:

   • Name: <name>

   • Class name: weblogic.xml.crypto.wss.UsernameTokenHandler

   • Token Type: ut

   • Handling Order: 1

   • Create a token handle for username token and configure the following:

   Create a token handler for X.509 and configure the following:

   • Name: <name>

   • Class name: weblogic.xml.crypto.wss.BinarySecurityTokenHandler

   • Token Type: x509

   • Handling Order: 0

   For the X.509 token handler, add the following properties:

   • Name: UserX509ForIdentity

   • Value: true

   • IsEncrypted: False

     For more information, see "Create a token handler of a Web Service security configuration" in Oracle WebLogic Server Administration Console Online Help.

7. Configure a credential mapping provider by creating a PKICredentialMapper and configure it as follows (leave all other values set to the defaults):

   • Keystore Provider: N/A

   • Keystore Type: jks

   • Keystore File Name: default_keystore.jks

   • Keystore Pass Phrase: <password>

   • Confirm Keystore Pass Phrase: <password>

     For more information, see "Configure Credential Mapping Providers" in Oracle WebLogic Server Administration Console Online Help

8. Configure Authentication by selecting the Authentication tab and configure as follows:

   • Click DefaultIdentityAsserter and add X.509 to Chosen active types

   • Click Provider Specific and configure the following:

   • Default User Name Mapper Attribute Type: CN

   • Active Types: X.509

   • Use Default User Name Mapper: True

9. If the users are not added, add the Common Name (CN) user specified in the certificate.

   For more information, see "Create users" in Oracle WebLogic Server Administration Console Online Help

10. Restart Oracle WebLogic Server.

11. Deploy the web service.

    For more information, see "Install a Web Service" in Oracle WebLogic Server Administration Console Online Help

Follow these steps to attach and configure the OWSM Client Policy:

1. Create a client proxy for the web service created earlier using clientgen or some other mechanism.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the client

   wss11_x509_token_with_message_protection_client_policy

3. Edit the policy as follows:

   <orasp:x509-token 
     orasp:sign-key-ref-mech="thumbprint"
     orasp:enc-key-ref-mech="thumbprint"/>

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

4. Provide the configuration for the server (encryption key) in the client.

   Note:

   Ensure that the encryption key specified is in accordance with the encryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server.

5. Invoke the web service method from the client.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

Follow these steps to attach and configure the OWSM Policy:

1. Create and deploy a web service.

   For more information, see "Roadmap for Implementing Oracle Fusion Middleware Web Services" in Understanding Web Services

2. Attach the following policy to the web service:

   oracle/wss11_x509_token_with_message_protection_service_policy.

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager

Follow these steps to attach and configure the WebLogic Web Service Client Policy:

1. Create a client proxy for the web service created earlier using clientgen.

   For more information, see "Using the clientgen Ant Task to Generate Client Artifacts" in Developing JAX-WS Web Services for Oracle WebLogic Server

2. Attach the following policies:

   • Wssp1.2-wss11_x509_token_with_message_protection_owsm_policy.xml

   • Wssp1.2-2007-SignBody.xml

   • Wssp1.2-2007-EncryptBody.xml

     For more information, see "Updating the JWS File with @Policy and @Policies Annotations" in Securing WebLogic Web Services for Oracle WebLogic Server

3. Provide the configuration for the server (encryption key) in the client.

   Note:

   Ensure that the encryption key specified is in accordance with the encryption key configured for the web service.

   For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" in Securing WebLogic Web Services for Oracle WebLogic Server

4. Invoke the web service method from the client.

   For more information, see "Writing the Java Client Application Code to Invoke a Web Service" in Developing JAX-WS Web Services for Oracle WebLogic Server