You can configure an OWSM 14c web service to implement username token with message protection for interoperability with an Axis and WSS4J client.

To configure the OWSM 14c web service:

1. Attach the following policy to the web service: 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.

2. Deploy the web service.

You can configure an Axis and WSS4J client to implement username token with message protection for interoperability with an OWSM 14c web service.

To configure an Axis and WSS4J client:

1. Build your web service client proxy.

2. Create the password callback class, PWCallback.java, and keystore properties file, crypto.properties.

   For more information, see Creating Required Files for Interoperability With Axis and WSS4J.

3. Include the keystore file (for example, default-keystore.jks) and crypto.properties file directly under the classes folder.

   Ensure that you are using keystore with v3 certificates. By default, the JDK 1.5 keytool generates keystores with v1 certificates.

4. Edit the deployment descriptor, client_deploy.wsdd, similar to the following client_deploy.wsdd deployment descriptor sample:

   <deployment xmlns="http://xml.apache.org/axis/wsdd/"
                xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
    <transport name="http" 
     pivot="java:org.apache.axis.transport.http.HTTPSender"/>
     <globalConfiguration >
      <!-- wss10_username_token_with_message_protection -->
      <requestFlow>
        <handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
          <parameter name="passwordCallbackClass" 
           value="com.oracle.xmlns.ConfigOverride_jws.CO_SOA.BPELProcess1.PWCallback"/>
          <parameter name="passwordType" value="PasswordText"/>
          <parameter name="user" value="weblogic"/>
          <parameter name="action" value="UsernameToken Timestamp Signature Encrypt"/>
          <parameter name="encryptionKeyTransportAlgorithm" 
           value="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"/>
          <parameter name="encryptionKeyIdentifier" value="DirectReference" />
          <parameter name="encryptionPropFile" value="crypto.properties" />
          <parameter name="encryptionUser" value="orakey" />
          <parameter name="encryptionParts" value=
       "{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}
        UsernameToken;{Content}{http://schemas.xmlsoap.org/soap/envelope/}Body" />
          <parameter name="signatureUser" value="orakey" />
          <parameter name="signaturePropFile" value="crypto.properties" />
          <parameter name="signatureKeyIdentifier" value="DirectReference" />
          <parameter name="signatureParts" value=
       "{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}
   UsernameToken;{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
   1.0.xsd}
   Timestamp;{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body" />
        </handler>
      </requestFlow>
      <responseFlow>
        <handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
          <parameter name="passwordCallbackClass" value="com.oracle.xmlns.ConfigOverride_jws.CO
   _SOA.BPELProcess1.PWCallback"/>
          <parameter name="action" value="Timestamp Signature Encrypt" />
          <parameter name="signaturePropFile" value="crypto.properties" />
          <parameter name="decryptionPropFile" value="crypto.properties" />
          <parameter name="enableSignatureConfirmation"  value="false" />
        </handler>
      </responseFlow>
     </globalConfiguration >
   </deployment>
   

   In the example, the receiver decrypts, verifies, and validates the username token; the sender inserts a username token, timestamp, signs the body, username token, and timestamp, and encrypts the body and username token. As shown in the example, the encryption key transport is overridden to match the OWSM default requirements

5. Set the following property within the client code to use the deployment descriptor defined in the previous step.

   System.setProperty("axis.ClientConfigFile", "client_deploy.wsdd");
   

6. Deploy the web service client.

You can configure an Axis and WSS4J web service to implement username token with message protection for interoperability with an OWSM 14c client.

To configure an Axis and WSS4J web service

1. Build your web service.

2. Create the password callback class, PWCallback.java, and keystore properties file, crypto.properties, as described in "Creating Required Files for Interoperability With Axis and WSS4J".

3. Include the keystore file (for example, default-keystore.jks) and crypto.properties file directly under the classes folder.

   Ensure that you are using keystore with v3 certificates. By default, the JDK 1.5 keytool generates keystores with v1 certificates.

4. Edit the deployment descriptor, server_deploy.wsdd, as shown in the following sample:

   <ns1:service name="HelloWorld" provider="java:RPC" style="wrapped" use="literal">
   <!-- wss10_username_token_with_message_protection -->
   <requestFlow>
      <handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
         <parameter name="passwordCallbackClass" value="PWCallback1"/>
         <parameter name="user" value="wss4j"/>
         <parameter name="action" value="Signature UsernameToken Timestamp Encrypt"/>
         <parameter name="signaturePropFile" value="crypto.properties" />
         <parameter name="decryptionPropFile" value="crypto.properties" />
      </handler>
   </requestFlow>
   <responseFlow>
      <handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
          <parameter name="passwordCallbackClass" value="PWCallback1"/>
          <parameter name="user" value="orakey"/>
          <parameter name="action" value="Timestamp Signature Encrypt"/>
          <parameter name="encryptionKeyTransportAlgorithm" 
             value="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"/>
          <parameter name="signaturePropFile" value="crypto.properties" />
          <parameter name="signatureKeyIdentifier" value="DirectReference" />
          <parameter name="signatureParts" 
   value="{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body;{Element}
   {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp" />
          <parameter name="encryptionKeyIdentifier" value="DirectReference" />
      </handler>
   </responseFlow>
   </ns1:service>
   

   In the example, the receiver decrypts, verifies, and validates the username token; the sender inserts a username token, timestamp, signs the body, username token, and timestamp, and encrypts the body and username token. As shown in the example, the encryption key transport is overridden to match the OWSM default requirements.

   Note:

   WSS4J enforces an order to the elements in the header. Ensure action ordering is updated in server_deploy.wsdd as shown in the sample.

5. Deploy the web service.

You can configure an OWSM 14c client to implement username token with message protection for interoperability with an Axis and WSS4J web service.

To configure an OWSM 14c client:

1. Attach the following policy to the web service: 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.

2. For Java SE clients only, configure the web service client properties, as follows:

   Note:

   This step is not required for Java EE clients.

   myPort.setProperty(ClientConstants.WSS_KEYSTORE_TYPE,"JKS");
   myPort.setProperty(ClientConstants.WSS_KEYSTORE_LOCATION,
    "/keystore-path/default-keystore.jks");
   myPort.setProperty(ClientConstants.WSS_KEYSTORE_PASSWORD, "password");
   myPort.setProperty(ClientConstants.WSS_RECIPIENT_KEY_ALIAS,"orakey");
   ...
   

   Where setProperty is defined as follows:

   public void setProperty(String name, String value) {
      ((Stub) _port)._setProperty(name, value);
   }
   

3. Deploy the web service client.

You can configure an OWSM 14c web service to implement SAML token for interoperability with an Axis and WSS4J client.

To configure the OWSM 14c web service:

1. 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.

2. Deploy the web service.

You can configure an Axis and WSS4J client to implement SAML token for interoperability with an OWSM 14c web service.

To configure an Axis and WSS4J client:

1. Build your web service client proxy.

2. Create the password callback class, PWCallback.java, keystore properties file, crypto.properties file, and saml.properties file, as described in Creating Required Files for Interoperability With Axis and WSS4J.

3. Include the keystore file (for example, default-keystore.jks) and crypto.properties file directly under the classes folder.

   Ensure that you are using keystore with v3 certificates. By default, the JDK 1.5 keytool generates keystores with v1 certificates.

4. Edit the deployment descriptor, client_deploy.wsdd, similar to the sample at the end of this procedure.

   In the example, the receiver decrypts, verifies, and validates the SAML token; the sender inserts a SAML token, timestamp, signs the body, SAML token, and timestamp, and encrypts the body. As shown in the example, the encryption key transport is overridden to match the OWSM default requirements.

5. Set the following property within the client code to use the deployment descriptor defined in the previous step.

   System.setProperty("axis.ClientConfigFile", "client_deploy.wsdd");
   

6. Deploy the web service client.

   See the following client_deploy.wsdd deployment descriptor sample:

   <deployment xmlns="http://xml.apache.org/axis/wsdd/"
                xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
    <transport name="http" 
     pivot="java:org.apache.axis.transport.http.HTTPSender"/>
     <globalConfiguration >
   <!-- wss10_saml_token_with_message_protection -->
       <requestFlow>
         <handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
           <parameter name="passwordCallbackClass" 
            value="com.oracle.xmlns.ConfigOverride_jws.CO_SOA.BPELProcess1.PWCallback"/>
           <parameter name="passwordType" value="PasswordText"/>
           <parameter name="user" value="weblogic"/>
           <parameter name="action" value="Timestamp Signature SAMLTokenSigned Encrypt"/>
           <parameter name="samlPropFile" value="saml.properties"/>
           <parameter name="encryptionKeyTransportAlgorithm" 
            value="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"/>
           <parameter name="encryptionKeyIdentifier" value="DirectReference" />
           <parameter name="encryptionPropFile" value="crypto.properties" />
           <parameter name="encryptionUser" value="orakey" />
           <parameter name="encryptionParts" 
            value="{Content}{http://schemas.xmlsoap.org/soap/envelope/}Body" />
           <parameter name="signatureUser" value="orakey" />
           <parameter name="signaturePropFile" value="crypto.properties" />
           <parameter name="signatureKeyIdentifier" value="DirectReference" />
           <parameter name="signatureParts" value="{Element}
             {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}
             Timestamp;{Element}
             {http://schemas.xmlsoap.org/soap/envelope/}Body" />
         </handler>
       </requestFlow>
       <responseFlow>
         <handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
           <parameter name="passwordCallbackClass" 
            value="com.oracle.xmlns.ConfigOverride_jws.CO_SOA.BPELProcess1.PWCallback" />
           <parameter name="action" value="Timestamp Signature Encrypt" />
           <parameter name="signaturePropFile" value="crypto.properties" />
           <parameter name="decryptionPropFile" value="crypto.properties" />
           <parameter name="enableSignatureConfirmation" value="false" />
       </handler>
     </responseFlow>
     </globalConfiguration >
   </deployment>
   

You can configure an Axis and WSS4J web service to implement SAML token with message protection for interoperability with an OWSM 14c client.

To configure Axis and WSS4J web service:

1. Build your web service.

2. Create the password callback class, PWCallback.java, keystore properties file, crypto.properties file, and saml.properties file as described in Creating Required Files for Interoperability With Axis and WSS4J.

3. Include the keystore file (for example, default-keystore.jks) and crypto.properties file directly under the classes folder.

   Ensure that you are using keystore with v3 certificates. By default, the JDK 1.5 keytool generates keystores with v1 certificates.

4. Edit the deployment descriptor, server_deploy.wsdd, as shown in the following sample:

   <ns1:service name="HelloWorld" provider="java:RPC" style="wrapped" use="literal">
   <!-- wss10_username_token_with_message_protection -->
   <requestFlow>
      <handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
         <parameter name="passwordCallbackClass" value="PWCallback1"/>
         <parameter name="user" value="wss4j"/>
         <parameter name="action" value="Signature SAMLTokenUnsigned Timestamp Encrypt"/>
         <parameter name="signaturePropFile" value="crypto.properties" />
         <parameter name="decryptionPropFile" value="crypto.properties" />
      </handler>
   </requestFlow>
   <responseFlow>
      <handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
          <parameter name="passwordCallbackClass" value="PWCallback1"/>
          <parameter name="user" value="orakey"/>
          <parameter name="action" value="Timestamp Signature Encrypt"/>
          <parameter name="encryptionKeyTransportAlgorithm" 
             value="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"/>
          <parameter name="signaturePropFile" value="crypto.properties" />
          <parameter name="signatureKeyIdentifier" value="DirectReference" />
          <parameter name="signatureParts" 
   value="{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body;{Element}
   {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp" />
          <parameter name="encryptionKeyIdentifier" value="DirectReference" />
      </handler>
   </responseFlow>
   </ns1:service>
   

   In the example, the receiver decrypts, verifies, and validates the SAML token; the sender inserts a SAML token, timestamp, signs the body, SAML token, and timestamp, and encrypts the body. As shown in the example, the encryption key transport is overridden to match the OWSM default requirements.

   Note:

   WSS4J enforces an order to the elements in the header. Ensure action ordering is updated in server_deploy.wsdd as shown in the sample.

5. Deploy the web service.

You can configure an OWSM 14c client to implement SAML token SSL for interoperability with an Axis and WSS4J web service.

To configure an OWSM 14c client:

1. Attach the following policy to the web service: 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.

2. For JSE clients only, configure the web service client properties, as follows:

   Note:

   This step is not required for Java EE clients.

   myPort.setProperty(ClientConstants.WSS_KEYSTORE_TYPE,"JKS");
   myPort.setProperty(ClientConstants.WSS_KEYSTORE_LOCATION,
    "/keystore-path/default-keystore.jks");
   myPort.setProperty(ClientConstants.WSS_KEYSTORE_PASSWORD, "password");
   myPort.setProperty(ClientConstants.WSS_RECIPIENT_KEY_ALIAS,"orakey");
   ...
   

   Where setProperty is defined as follows:

   public void setProperty(String name, String value) {
      ((Stub) _port)._setProperty(name, value);
   }
   

3. Deploy the web service client.

You can configure an OWSM 14c web service to implement username token over SSL for interoperability with an Axis and WSS4J client.

To configure OWSM 14c web service:

1. Configure the server for SSL.

   For more information, see "Configuring Transport-Level Security (SSL)" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

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

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

3. Deploy the web service.

You can configure an Axis and WSS4J client to implement username token over SSL for interoperability with an OWSM 14c web service.

To configure an Axis and WSS4J client:

1. Build your web service client proxy.

2. Create the password callback class, PWCallback.java, and keystore properties file, crypto.properties, as described in Creating Required Files for Interoperability With Axis and WSS4J.

3. Edit the deployment descriptor, client_deploy.wsdd, similar the example below. In the example, the receiver validates the username token and timestamp; the sender inserts a timestamp.

   <deployment xmlns="http://xml.apache.org/axis/wsdd/"
                xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
    <transport name="http" 
     pivot="java:org.apache.axis.transport.http.HTTPSender"/>
   <globalConfiguration >
   <!-- wss_username_token -->
   <requestFlow >
      <handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
         <parameter name="action" value="UsernameToken Timestamp"/>
         <parameter name="user" value="weblogic"/>
         <parameter name="passwordCallbackClass" 
          value="com.oracle.xmlns.ConfigOverride_jws.CO_SOA.BPELProcess1.PWCallback"/>
         <parameter name="passwordType" value="PasswordText"/>
     </handler>
   </requestFlow >
   </globalConfiguration >
   </deployment>
   

4. Set the following property within the client code to use the deployment descriptor defined in the previous step.

   System.setProperty("axis.ClientConfigFile", "client_deploy.wsdd");
   

5. Deploy the web service client.

You can configure an Axis and WSS4J web service to implement username token over SSL for interoperability with an OWSM 14c client.

To configure the Axis and WSS4J web service:

1. Configure the server for SSL.

2. Build your web service.

3. Create the password callback class, PWCallback.java, and crypto.properties file, as described in Creating Required Files for Interoperability With Axis and WSS4J.

4. Edit the deployment descriptor, server_deploy.wsdd, similar to the example below. In the example, the receiver validates the username token and the timestamp; the sender inserts a timestamp.

   <ns1:service name="HelloWorld" provider="java:RPC" style="wrapped" 
    use="literal">
   <!-- wss_username_token_over_ssl -->
     <requestFlow>
       <handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
         <parameter name="passwordCallbackClass" value="PWCallback1"/>
         <parameter name="action" value="Timestamp UsernameToken"/>
       </handler>
     </requestFlow>
     <responseFlow> 
        <handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
         <parameter name="action" value="Timestamp"/>
         </handler>
     </responseFlow>
   </ns1:service>
   

5. Deploy the web service.

You can configure an OWSM 14c client to implement username token over SSL for interoperability with an Axis and WSS4J web service.

To configure an OWSM 14c client:

1. Attach the following policy to the web service client: wss_username_token_over_ssl_client_policy.

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

2. For JSE clients only, configure the web service client properties, as shown below. The username and password must be set by the client for generating the username token.

   Note:

   This step is not required for Java EE clients.

   myPort.setUsername("wss4j");
   myPort.setPassword("security"););
   

3. Deploy the web service client.

   When running the client, include the following client system property, where default-keystore.jks specifies the keystore that contains the certificate corresponding to the server certificate.

   -Djavax.net.ssl.trustStore=default-keystore.jks
   

You can configure an OWSM 14c web service to implement SAML token sender vouches over SSL for interoperability with an Axis and WSS4J client.

To configure the OWSM 14c web service:

1. Configure the server for SSL.

   For more information, see "Configuring Transport-Level Security (SSL)" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

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

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

3. Deploy the web service.

You can configure an Axis and WSS4J client to implement SAML token sender vouches over SSL for interoperability with an OWSM 14c web service.

To configure an Axis and WSS4J client:

1. Build your web service client proxy.

2. Create the password callback class, PWCallback.java; keystore properties file, crypto.properties; and SAML properties file, saml.properties, as described in Creating Required Files for Interoperability With Axis and WSS4J.

3. Edit the deployment descriptor, client_deploy.wsdd, similar the example below. In the example, the receiver validates the SAML token and timestamp; the sender inserts a timestamp.

   <deployment xmlns="http://xml.apache.org/axis/wsdd/"
                xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
   <transport name="http" 
     pivot="java:org.apache.axis.transport.http.HTTPSender"/>
    <globalConfiguration >
   <!-- wss_saml_token -->
   <requestFlow >
      <handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
         <parameter name="action" value="SAMLTokenSigned Timestamp"/>
         <parameter name="samlPropFile" value="saml.properties"/>
         <parameter name="user" value="weblogic"/>
         <parameter name="passwordCallbackClass"
    value="com.oracle.xmlns.ConfigOverride_jws.CO_SOA.BPELProcess1.PWCallback"/>
         <parameter name="passwordType" value="PasswordText"/>
         <parameter name="signatureUser" value="orakey" />
         <parameter name="signatureKeyIdentifier" value="DirectReference" />
         <parameter name="signaturePropFile" value="crypto.properties" />
      </handler>
   </requestFlow >
   </globalConfiguration >
   </deployment>
   

4. Set the following property within the client code to use the deployment descriptor defined in the previous step.

   System.setProperty("axis.ClientConfigFile", "client_deploy.wsdd");
   

5. Deploy the web service client.

You can configure an Axis and WSS4J web service to implement SAML token sender vouches over SSL for interoperability with an OWSM 14c client.

To configure the Axis and WSS4J web service:

1. Configure the server for SSL.

2. Build your web service.

3. Create the password callback class, PWCallback.java, and crypto.properties file, as described in Creating Required Files for Interoperability With Axis and WSS4J.

4. Edit the deployment descriptor, server_deploy.wsdd, similar to the example below.

   In the example, the receiver validates the SAML token and the timestamp; the sender inserts a timestamp.

   <ns1:service name="HelloWorld" provider="java:RPC" style="wrapped" 
    use="literal">
   <!-- wss_saml_token_over_ssl -->
   <requestFlow>
      <handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
         <parameter name="passwordCallbackClass" value="PWCallback1"/>
         <parameter name="action" value="Timestamp SAMLTokenUnsigned"/>
      </handler>
   </requestFlow>
   <responseFlow>
      <handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
         <parameter name="action" value="Timestamp"/>
      </handler>
   </responseFlow>
   </ns1:service>
   

5. Deploy the web service.

You can configure an OWSM 14c client to implement SAML token sender vouches over SSL for interoperability with an Axis and WSS4J web service.

To configure the OWSM 14c client:

1. Attach the following policy to the web service client: wss_saml_token_over_ssl_client_policy.

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

2. For JSE clients, configure the web service client properties, as shown below. The username must be set by the client for generating the SAML assertion.

   myPort.setUsername("wss4j");
   

   Note:

   This step is not required for Java EE clients.

3. Deploy the web service client.

   When running the client, include the following client system property, where default-keystore.jks specifies the keystore that contains the certificate corresponding to the server certificate.

   -Djavax.net.ssl.trustStore=default-keystore.jks