Skip to main content

developerWorks >  SOA and Web services  >  Forums  >  Web Services Technical  >  developerWorks

com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5048E: One of "SOA    Point your RSS reader here for a feed of the latest messages in this thread


     

 
 

My developerWorks
 Welcome, Guest
Sign in or register
This question is not answered.

Permlink Replies: 2 - Pages: 1 - Last Post: Oct 12, 2009 5:01 PM Last Post By: Barbara_Jensen
Debashis

Posts: 1
Registered: Mar 20, 2008 06:09:11 AM
com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5048E: One of "SOA
Posted: Mar 20, 2008 06:13:15 AM
 
Click to report abuse...   Click to reply to this thread Reply
I want to call WCC(Websphere Customer Center ) exposed webservices via Axis 1.4 utility (WSDL2Java) generated
stubs. while calling I'm getting 'com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5048E: One of "SOAP Header" elements required' error. Global security is disabled. please help me out of this.
davidrsetti

Posts: 3
Registered: Aug 06, 2007 03:56:52 PM
Re: com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5048E: One of "SOA
Posted: Jun 06, 2008 01:53:36 PM   in response to: Debashis in response to: Debashis's post
 
Click to report abuse...   Click to reply to this thread Reply
I have a similar issue, I am usign scope scope. Global Security is on. I've even used the attentication cookie passed .
SOAP Body
{
Fault Fault
{
QName faultcode = soapenv:Server.securityException
string faultstring = com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5048E: One of "SOAP Header" elements required.

detail detail
{
}
}
}
Barbara_Jensen

Posts: 6
Registered: Apr 26, 2005 06:56:43 PM
Re: com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5048E: One of "SOA
Posted: Oct 12, 2009 05:01:45 PM   in response to: Debashis in response to: Debashis's post
 
Click to report abuse...   Click to reply to this thread Reply
This tells me that:

1) It is a JAX-RPC provider
2) WS-Security constraints are applied to the application
3) There are no SOAP headers at all in the SOAP message (checking for the WS-Security header is later in the code)

When WS-Security constraints are applied to an application, a SOAP message that meets the constraints must be posted. If a WS-Security header is not included in the SOAP message at all, then the constraints have obviously not been met.

You need to find out what the WS-Security configuration is of the provider application, then apply the complimentary constraints to your consumer application.

Point your RSS reader here for a feed of the latest messages in all forums