aspose file tools*
The moose likes Web Services and the fly likes WS Security Username Token Issue with Weblogic Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "WS Security Username Token Issue with Weblogic" Watch "WS Security Username Token Issue with Weblogic" New topic
Author

WS Security Username Token Issue with Weblogic

Subhajit Majumdar
Greenhorn

Joined: Nov 09, 2006
Posts: 5
Hi,



I am trying to implement WS-Security (Username Token) on web services deployed on Weblogic Server 8.1 (sp4). The deployment works fine but whenever I try to invoke the service using auto generated client stub (created using clientgen) or weblogic server console (service test page) , I get the following error:



<Nov 8, 2006 12:01:46 PM GMT+05:30> <Info> <WebService> <BEA-220024> <Handler weblogic.webservice.core.handler.WSSEClientHandler threw an exception from its handleRequest method. The exception was:

java.lang.AssertionError: Bad password type: wsse asswordText.>

Failed to create web service client:java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.lang.AssertionError: Bad password type: wsse asswordText (see Fault Detail for stacktrace)

Detail:

<detail>

<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.lang.AssertionError: Bad password type: wsse asswordText

at weblogic.xml.security.wsse.v200207.UsernameTokenImpl.<init>(UsernameTokenImpl.java:64)

at weblogic.xml.security.wsse.v200207.SecurityElementFactoryImpl.createToken(SecurityElementFactoryImpl.java:59)

at weblogic.webservice.core.handler.WSSEClientHandler.processSpecs(WSSEClientHandler.java:300)

at weblogic.webservice.core.handler.WSSEClientHandler.handleRequest(WSSEClientHandler.java:100)

at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:143)

at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:231)

at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)

at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)

at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)

at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:303)

at com.cts.sipservices.implementation.client.MrmPartyServiceImplementationPort_Stub.getParty(MrmPartyServiceImplementationPort_Stub.java:46)

at com.cts.sipservicesclient.client.SecureClient.<init>(SecureClient.java:76)

at com.cts.sipservicesclient.client.SecureClient.main(SecureClient.java:38)

</bea_fault:stacktrace>

</detail>; nested exception is:

javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.lang.AssertionError: Bad password type: wsse asswordText (see Fault Detail for stacktrace)





This is the �security� tag of my �web-services.xml�:



<security>

<spec:SecuritySpec xmlns:spec="http://www.openuri.org/2002/11/wsse/spec"

Namespace="http://schemas.xmlsoap.org/ws/2002/07/secext"

Id="default-spec">

<spec:UsernameTokenSpec xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"

PasswordType="wsse asswordText">

</spec:UsernameTokenSpec>

</spec:SecuritySpec>

</security>



Thanks
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 42608
    
  65
Instead of "wsse:PasswordText", have you tried just "PasswordText"? Weblogic may be different, but that's what WSS4J uses.


Ping & DNS - my free Android networking tools app
Subhajit Majumdar
Greenhorn

Joined: Nov 09, 2006
Posts: 5
But, weblogic documentation says that it should be wsse asswordText. Anyway, I will try what you said.
Subhajit Majumdar
Greenhorn

Joined: Nov 09, 2006
Posts: 5
No, "PasswordText" doesn't work.
Subhajit Majumdar
Greenhorn

Joined: Nov 09, 2006
Posts: 5
Hi,

Can anyone help me out with this thing?

Exception Stack Trace:

<Nov 10, 2006 12:19:43 PM GMT+05:30> <Info> <WebService> <BEA-220024> <Handler weblogic.webservice.core.handler.WSSEClientHandler threw an exception from its handleRequest method. The exception was:
java.lang.AssertionError: Bad password type: wsse:PasswordText.>
Failed to create web service client:java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.lang.AssertionError: Bad password type: wsse:PasswordText (see Fault Detail for stacktrace)
Detail:
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.lang.AssertionError: Bad password type: wsse:PasswordText
at weblogic.xml.security.wsse.v200207.UsernameTokenImpl.<init>(UsernameTokenImpl.java:64)
at weblogic.xml.security.wsse.v200207.SecurityElementFactoryImpl.createToken(SecurityElementFactoryImpl.java:59)
at weblogic.webservice.core.handler.WSSEClientHandler.processSpecs(WSSEClientHandler.java:300)
at weblogic.webservice.core.handler.WSSEClientHandler.handleRequest(WSSEClientHandler.java:100)
at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:143)
at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:231)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:303)
at com.cts.sipservices.implementation.client.MrmPartyServiceImplementationPort_Stub.getParty(MrmPartyServiceImplementationPort_Stub.java:46)
at com.cts.sipservicesclient.client.SecureClient.<init>(SecureClient.java:68)
at com.cts.sipservicesclient.client.SecureClient.main(SecureClient.java:30)
</bea_fault:stacktrace>
</detail>; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.lang.AssertionError: Bad password type: wsse:PasswordText (see Fault Detail for stacktrace)


The 'Security' Element of the web-services.xml

<security>
<spec:SecuritySpec xmlns:spec="http://www.openuri.org/2002/11/wsse/spec"
Namespace="http://schemas.xmlsoap.org/ws/2002/07/secext"
Id="default-spec">
<spec:UsernameTokenSpec xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"
PasswordType="wsse:PasswordText">
</spec:UsernameTokenSpec>
</spec:SecuritySpec>
</security>

Thanks
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WS Security Username Token Issue with Weblogic