Difficulty in WS_security

Question

I am using Workshop vesrion 8.1.4. I have coded an application exactly similar to the security.wsse.reqResp.mycompany.MyCompany & security.wsse.reqResp.client.Client in sample directory which comes with Workshop. I am using the exactly the same key store used in the sample. The sample programs work fine, while something I did exactly similar to samples is not working.
The problem is when I run the client, it does not seem to apply the policies resulting in the error
below. I am not sure why it is not applying signature as per the policy file defined for the control used in the client. Thnakful, if some one can help. Can provide more info, if needed. Thnaks.
<faultcode> SOAP-ENV:Client </faultcode>
<faultstring> EJB Exception: ; nested exception is:
com.bea.wlw.runtime.jws.wssecurity.exception.WLWWSSEException: Policy requires Message to be signed, Message was not signed. </faultstring>
<detail>
java.rmi.RemoteException: EJB Exception: ; nested exception is:
com.bea.wlw.runtime.jws.wssecurity.exception.WLWWSSEException: Policy requires Message to be signed, Message was not signed.
at weblogic.ejb20.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:102)
On the service side, I have the following jws file:
package security.wsse.reqresp.service;
* @jws:ws-security-service file="MyCompanySecurityPolicy.wsse"
* @common:target-namespace namespace="http://workshop.bea.com/MyCompany"
public class GreetGuest implements com.bea.jws.WebService
static final long serialVersionUID = 1L;
* @common:operation
public String SayHello(String aGuest)
return "Welcome " + aGuest + " This is a Secure Service";
The policy is exactly as in the sample ( in fact I cut and pasted from sample)
<wsSecurityPolicy xsi:schemaLocation="WSSecurity-policy.xsd" xmlns="http://www.bea.com/2003/03/wsse/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <wsSecurityOut>
<!--
Accompany the SOAP message with a valid username and password
-->
<userNameToken>
<userName>weblogic</userName>
<password type="TEXT">weblogic</password>
</userNameToken>
<!--
Encrypt the SOAP message with the recipient's (MyCompany.jws) public key.
Only the recipient's private key can decrypt it.
Ensures the confidentiality of the SOAP message.
(This process requires that the sender's keystore already contains
a digital certificate containing the recients public key.)
-->
          <encryption>
               <encryptionKey>
                    <alias>mycompany</alias>
               </encryptionKey>
          </encryption>
<!--
Sign the SOAP message with the sender's (Client.jws) private key.
Only the sender's public key can validate the signature.
Ensures the authenticity of the sender, i.e., that the sender is
in fact the source of the SOAP message.
-->
<signatureKey>
               <alias>client1</alias>
               <password>password</password>
          </signatureKey>
     </wsSecurityOut>
<wsSecurityIn>
<!--
Incoming SOAP message must be accompanied by a valid username
and password.
-->
          <token tokenType="username"/>
<!--
Incoming SOAP messages must be encrypted with client.jws's
public key. The alias and password to access the client.jws's
decrypting private key in the keystore are provided by
the <decryptionKey> element below.
-->
          <encryptionRequired>
               <decryptionKey>
                    <alias>client1</alias>
                    <password>password</password>
               </decryptionKey>
          </encryptionRequired>
<!--
Incoming SOAP messages must be digitally signed with the sender's
private key.
The sender's public key is used to validate the signature.
-->
          <signatureRequired>true</signatureRequired>
</wsSecurityIn>
<!--
Look for the client.jks keystore in the default location, the server domain
root, in this case, BEA_HOME\weblogic81\samples\domains\workshop.
-->
     <keyStore>
<keyStoreLocation>samples_client.jks</keyStoreLocation>
<keyStorePassword>password</keyStorePassword>
</keyStore>
</wsSecurityPolicy>
on the client side:
I have jws :
package security.wsse.reqresp.client;
* @common:target-namespace namespace="http://workshop.bea.com/Client"
public class Client implements com.bea.jws.WebService
* @common:control
private security.wsse.reqresp.client.SecuredGreeting securedGreetingControl;
* @common:control
private security.wsse.reqresp.client.GreetGuest greetGuestControl;
static final long serialVersionUID = 1L;
* @common:operation
public void getGreeted(String myName)
String aReturnValue = securedGreetingControl.SayHello(myName);
System.out.println("Message from Service=" + aReturnValue );
The control in the client , I used is:
package security.wsse.reqresp.client;
* @jc:location http-url="http://localhost:7001/TestWebServicesProject/security/wsse/reqresp/service/GreetGuest.jws"
* @jc:wsdl file="#GreetGuestWsdl"
* @editor-info:link autogen-style="java" source="GreetGuestContract.wsdl" autogen="true"
public interface SecuredGreeting extends com.bea.control.ControlExtension, com.bea.control.ServiceControl
public java.lang.String SayHello (java.lang.String aGuest);
static final long serialVersionUID = 1L;
/** @common:define name="GreetGuestWsdl" value::
<?xml version="1.0" encoding="utf-8"?>
<!-- @editor-info:link autogen="true" source="GreetGuest.jws" -->
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://workshop.bea.com/MyCompany" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://workshop.bea.com/MyCompany">
<types>
<s:schema elementFormDefault="qualified" targetNamespace="http://workshop.bea.com/MyCompany" xmlns:s="http://www.w3.org/2001/XMLSchema">
<s:element name="SayHello">
<s:complexType>
<s:sequence>
<s:element name="aGuest" type="s:string" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="SayHelloResponse">
<s:complexType>
<s:sequence>
<s:element name="SayHelloResult" type="s:string" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="string" nillable="true" type="s:string"/>
</s:schema>
</types>
<message name="SayHelloSoapIn">
<part name="parameters" element="s0:SayHello"/>
</message>
<message name="SayHelloSoapOut">
<part name="parameters" element="s0:SayHelloResponse"/>
</message>
<message name="SayHelloHttpGetIn">
<part name="aGuest" type="s:string"/>
</message>
<message name="SayHelloHttpGetOut">
<part name="Body" element="s0:string"/>
</message>
<message name="SayHelloHttpPostIn">
<part name="aGuest" type="s:string"/>
</message>
<message name="SayHelloHttpPostOut">
<part name="Body" element="s0:string"/>
</message>
<portType name="GreetGuestSoap">
<operation name="SayHello">
<input message="s0:SayHelloSoapIn"/>
<output message="s0:SayHelloSoapOut"/>
</operation>
</portType>
<portType name="GreetGuestHttpGet">
<operation name="SayHello">
<input message="s0:SayHelloHttpGetIn"/>
<output message="s0:SayHelloHttpGetOut"/>
</operation>
</portType>
<portType name="GreetGuestHttpPost">
<operation name="SayHello">
<input message="s0:SayHelloHttpPostIn"/>
<output message="s0:SayHelloHttpPostOut"/>
</operation>
</portType>
<binding name="GreetGuestSoap" type="s0:GreetGuestSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="SayHello">
<soap:operation soapAction="http://workshop.bea.com/MyCompany/SayHello" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<binding name="GreetGuestHttpGet" type="s0:GreetGuestHttpGet">
<http:binding verb="GET"/>
<operation name="SayHello">
<http:operation location="/SayHello"/>
<input>
<http:urlEncoded/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
</binding>
<binding name="GreetGuestHttpPost" type="s0:GreetGuestHttpPost">
<http:binding verb="POST"/>
<operation name="SayHello">
<http:operation location="/SayHello"/>
<input>
<mime:content type="application/x-www-form-urlencoded"/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
</binding>
<service name="GreetGuest">
<port name="GreetGuestSoap" binding="s0:GreetGuestSoap">
<soap:address location="http://localhost:7001/TestWebServicesProject/security/wsse/reqresp/service/GreetGuest.jws"/>
</port>
<port name="GreetGuestHttpGet" binding="s0:GreetGuestHttpGet">
<http:address location="http://localhost:7001/TestWebServicesProject/security/wsse/reqresp/service/GreetGuest.jws"/>
</port>
<port name="GreetGuestHttpPost" binding="s0:GreetGuestHttpPost">
<http:address location="http://localhost:7001/TestWebServicesProject/security/wsse/reqresp/service/GreetGuest.jws"/>
</port>
</service>
</definitions>
The policy file for the control is:
<wsSecurityPolicy xsi:schemaLocation="WSSecurity-policy.xsd" xmlns="http://www.bea.com/2003/03/wsse/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <wsSecurityOut>
<!--
Accompany the SOAP message with a valid username and password
-->
<userNameToken>
<userName>weblogic</userName>
<password type="TEXT">weblogic</password>
</userNameToken>
<!--
Encrypt the SOAP message with the recipient's (MyCompany.jws) public key.
Only the recipient's private key can decrypt it.
Ensures the confidentiality of the SOAP message.
(This process requires that the sender's keystore already contains
a digital certificate containing the recients public key.)
-->
          <encryption>
               <encryptionKey>
                    <alias>mycompany</alias>
               </encryptionKey>
          </encryption>
<!--
Sign the SOAP message with the sender's (Client.jws) private key.
Only the sender's public key can validate the signature.
Ensures the authenticity of the sender, i.e., that the sender is
in fact the source of the SOAP message.
-->
<signatureKey>
               <alias>client1</alias>
               <password>password</password>
          </signatureKey>
     </wsSecurityOut>
<wsSecurityIn>
<!--
Incoming SOAP message must be accompanied by a valid username
and password.
-->
          <token tokenType="username"/>
<!--
Incoming SOAP messages must be encrypted with client.jws's
public key. The alias and password to access the client.jws's
decrypting private key in the keystore are provided by
the <decryptionKey> element below.
-->
          <encryptionRequired>
               <decryptionKey>
                    <alias>client1</alias>
                    <password>password</password>
               </decryptionKey>
          </encryptionRequired>
<!--
Incoming SOAP messages must be digitally signed with the sender's
private key.
The sender's public key is used to validate the signature.
-->
          <signatureRequired>true</signatureRequired>
</wsSecurityIn>
<!--
Look for the client.jks keystore in the default location, the server domain
root, in this case, BEA_HOME\weblogic81\samples\domains\workshop.
-->
     <keyStore>
<keyStoreLocation>samples_client.jks</keyStoreLocation>
<keyStorePassword>password</keyStorePassword>
</keyStore>
</wsSecurityPolicy>

Answer 1

Hi Vijay
It appears like you are not applying the wsse policy on the client side.
Check the jws as well as the control on the Client side. Both do not refer to a wsse policy file
Your code snippets:
Jws:
* @common:target-namespace namespace="http://workshop.bea.com/Client"
public class Client implements com.bea.jws.WebService
Service Control:
* @jc:location http-url="http://localhost:7001/TestWebServicesProject/security/wsse/reqresp/service/GreetGuest.jws"
* @jc:wsdl file="#GreetGuestWsdl"
* @editor-info:link autogen-style="java" source="GreetGuestContract.wsdl" autogen="true"
public interface SecuredGreeting extends com.bea.control.ControlExtension, com.bea.control.ServiceControl
Please refer to the wsse file on the Client side just like how you have done it on the server side.
Vimala-