I need to secure SOAP message sent into SOAP adapter, how to?

Hi guys,
My scenario uses SOAP and I need to secure this SOAP message sent into SOAP adapter. As I have read in the documentation, HTTPS is possible only on the SOAP receiver adapter. But my is SENDER.
COuld you help me please, how to solve it? Or post some link? Or, if you have your own approach, to let me know?
Thanx, Peter

Hi,
you can use SSL with the sender adapter. Please see the extract of the SOAP Adapter FAQ (Note #856597) below:
<b>Q:</b> Can I use SSL for my sender adapter?
<b>A:</b> Yes. Normally, the SOAP adapter servlet runs on the engines HTTP port. But you can activate the engine's HTTPS port so that this servlet can receive messages sent to the HTTPS port. See the documentation about the J2EE engine's security configuration.
I am afraid, I haven't yet tried this myself, so you will need to consult the J2EE documentation.
Regards,
HC

Similar Messages

How to get soap message sent out

Hi,
I used a client proxy in ABAP to consume a web service.
However I got errors saying there is 'Unexpected elemement' in SOAP message.
To find out the root cause, i would like to get the soap message sent out from the proxy.
Is there any way to do that?

Thanks to all your guys

Help, how to monitor the soap message sent by JAX-WS

Hi,everyone:
I want to monitor the soap message sent by JAX-WS using apache TCPMon.
For example, the JAX-WS is deployed on port 8080 , I make TCPMon listening on port 4444 and send soap request to port 4444 using JAX-WS.
Code in client:
@WebServiceClient(name = "JAX_WS", targetNamespace = "http://www.example.org/JAX_WS/", wsdlLocation = "file:/E:/zwz/EclipseWorkspace/JAX_WSDemo/WebRoot/META-INF/JAX_WS.wsdl")
public class JAXWS_Service extends Service {
     private final static URL JAXWS_WSDL_LOCATION;
     private final static Logger logger = Logger
               .getLogger(demo.client.JAXWS_Service.class.getName());
     static {
          URL url = null;
          try {
               //URL baseUrl;
               //baseUrl = demo.client.JAXWS_Service.class.getResource(".");
               url = new URL("http://localhost:4444/JAX_WSDemo/JAXWSBean");
          } catch (MalformedURLException e) {
               logger
                         .warning("Failed to create URL for the wsdl Location: 'file:/E:/zwz/EclipseWorkspace/JAX_WSDemo/WebRoot/META-INF/JAX_WS.wsdl', retrying as a local file");
               logger.warning(e.getMessage());
          JAXWS_WSDL_LOCATION = url;
     public JAXWS_Service(URL wsdlLocation, QName serviceName) {
          super(wsdlLocation, serviceName);
     public JAXWS_Service() {
          super(JAXWS_WSDL_LOCATION, new QName("http://www.example.org/JAX_WS/","JAXWSBeanService")); //JAX_WS
     @WebEndpoint(name = "JAX_WSPort")
     public JAXWS getJAXWSSOAP() {
          return super.getPort(new QName("http://www.example.org/JAX_WS/","JAX_WSPort"), JAXWS.class); //JAX_WSSOAP
}But i get the exception:
Exception in thread "main" com.sun.xml.internal.ws.wsdl.parser.InaccessibleWSDLException: 2 counts of InaccessibleWSDLException.
java.net.SocketException: Unexpected end of file from server
java.net.SocketException: Unexpected end of file from serverAnd the TCPMon doesn't receive anything.
If i use Axis2, the TCPMon will work fine.
I cannot figure out how to configure the webservices.
Could anyone help me? Thanks a lot.

[http://blog.vinodsingh.com/2007/02/monitor-soap-messages.html|http://blog.vinodsingh.com/2007/02/monitor-soap-messages.html]
Edited by: vinod.singh on 7 Apr, 2009 11:03 AM

I forgot my apple Security Question. So when I Redeem Some money to my account and I want to purchase it's need the security question, I forget it. So how could I reset my security question of apple ID?

I forgot my apple Security Question. So when I Redeem Some money to my account and I want to purchase it's need the security question, I forget it. So how could I reset my security question of apple ID?

1. See my User Tip for some help: Some Solutions for Resetting Forgotten Security Questions: Apple Support Communities.
2. Here are two different but direct methods:
    a. Send Apple an email request at: Apple - Support - iTunes Store - Contact Us.
    b. Call Apple Support in your country: Customer Service: Contacting Apple for support
        and service.
3. For other queries about Apple ID see Frequently asked questions about Apple ID.
4. Rescue email address and how to reset Apple ID security questions

How to get full SOAP message sent from XI to web srvice

Hi guys!
In my scenario IDoc->XI->SOAP I need to see the SOAP message, which arrives into target web service. Where can I see it? I suppose in sxmb monitor, but which part? I can not find it...
Thanx, Olian

In MONi you will only be able to see the XML payload or rather the SOAP Body.
If you want to see the entire HTTP post message used by the SOAP adapter will the SOAP Enevlope you need to use either,
1. The TCP Gateway as shown in Stefan's Blog
or,
2. Follow the instructions in this thread. You would need to turn on Synch Logging in the Visual Admin for this though,
Monitoring SOAP Message Payload
I would suggest you follow Stefan's blog as it is quite simple rather than turning on Synch Logging in the Va.
Regards
Bhavesh

Workshop - How to send a SOAP message directly into a JMS qeue......

Hi All,
I need to create a web service in Workshop that sends the received SOAP message
body to a queue without mapping it to Java object i.e. the JMS message type is
text message and not Object message. I would very much appreciated if anyone out
there who can advise me on this.
Thanks in advance.
Regards,
Boon Keong

Hi,
Are you open for other solutions besides Workshop?
WebLogic Server provides another Web Service implementation outside of Workshop.
This web service implentation has a concept of handlers which intercept SOAP
messages. It is a way to gain access to the SOAP message. You could then route
the SOAP message to a JMS queue from the handler.
These URLs will help:
http://e-docs.bea.com/wls/docs70/webserv/index.html
http://e-docs.bea.com/wls/docs70/webserv/design.html#1053805
Also, there is an examples in the WebLogic Server 7.0 installation:
%BEA_HOME%\samples\server\src\examples\webservices\handler
hope this helps,
pat
"Boon Keong" <[email protected]> wrote:
>
Hi All,
I need to create a web service in Workshop that sends the received SOAP
message
body to a queue without mapping it to Java object i.e. the JMS message
type is
text message and not Object message. I would very much appreciated if
anyone out
there who can advise me on this.
Thanks in advance.
Regards,
Boon Keong

Printing SOAP message sent / received

We've developed a web service that allows a client to send and receive the expected data from a java and a .net client. We're having a problem however when instantiating an object to pass as a param to the webservice from the .net client. It works fine with java primitive type or String - we've tested this. But when we create a class that has a three strings as attributes, none of the params are getting across - the object isn't null, its just marshalled or unmarshalled incorrectly (we think).
What I need to know is how to turn on some type of verbosity so I can see the soap message when using the external .net client? I can see the message fine on the java side, but not when invoking from .net.

You could also monitor this from the .NET client end. One approach is to
write a SOAP extension to intercept the AfterSerialize and BeforeDeserialize
events. Here's a sample code that logs the SOAP request and response:
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconalteringsoapmessag
eusingsoapextensions.asp
Jorge
"Andrew Bray" <[email protected]> wrote in message
news:[email protected]..
We've developed a web service that allows a client to send and receive theexpected data from a java and a .net client. We're having a problem however
when instantiating an object to pass as a param to the webservice from the
.net client. It works fine with java primitive type or String - we've
tested this. But when we create a class that has a three strings as
attributes, none of the params are getting across - the object isn't null,
its just marshalled or unmarshalled incorrectly (we think).
>
What I need to know is how to turn on some type of verbosity so I can seethe soap message when using the external .net client? I can see the message
fine on the java side, but not when invoking from .net.

Async r3- xi- soap problem.. no soap msg sent from SOAP receiver adapter

Hi guys!
I have an issue with SOAP scenario. I have ABAP Proxy->XI->SOAP async scenario. When I send msgfrom r3, it arrives into XI, but no SOAP message is sent to the target url. In the SXMB monitor, the flag is delivered The status of adapter is not valid. error: target url is invalid. messages crash at timeout. But when I test it from other tools, the target web service worx fine. One more info: we use stand-alone adpater engine. I tried it also on the integrated one, but it didn't work.
Sync scenarios work fine: SOAP->XI->R3->XI->SOAP.
Any ideas, what could be wrong? Are there some special requirements, for message interfaces (do they need 2 b sync??) or something else?
Thanx, Olian.

Hi Michal!
First, I even didn't know about this monitoring tool it's gr8.
Well, I found error: MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction:
Any idea?
I'm going to study something about it, but if you know, let me pls info!
Thanx a lot!
Olian

WS Addressing elements in a SOAP request sent via SOAP sender adapter

Hi guys,
I have a requirement (Proxy->PI->SOAP) for sending a soap request using the WS addressing elements in the request header. As I went through a documentation to SOAP sender adpter there is no option for this. WS-A is supported in the WS adapter, but the target web service does not support WS-RM, so this is not an option.
Do you have any hint?
Thanks,
Peter

You can create your own SOAP header in mapping or use Axis framework for this.
Regards
Stefan

Change encoding of input message sent by J2EE Adapter

Hi all,
I get a input message with a wrong encoding (Sender SMTP Adapter). Within XML prolog, there's a declaration of UTF-8. Having a look at the message, it's ISO-8859-1 encoded. That mean's I've to do one of the following options:
a) change encoding declaration in XML prolog to the correct one: ISO-8859-1
b) reencode the entire message from ISO-8859-1 into UTF-8, so that the message encoding matches the XML prolog
I've found two possible solutions, but I don't know if they're working:
1. usage of XMLAnomyzerModule: reading the documentation, it seems to be that I cannot use that module in a sender adapter, right? If I'm wrong: what does the module do? Does it just exchange the encoding declaration in the prolog or does it reencode the message?
2. running that small XSLT mapping before my own mapping: would it change the encoding declaration from UTF-8 to ISO-8859-1 in the XML prolog?
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" encoding="ISO-8859-1"/>
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>
BR
Holger

Hi Stefan,
thanks for your reply. Unfortunately it's not my application who's sending the wrong message and it's not possible to change it on sender side. I don't know why but it's like that
So it's exactly like you've mentioned: when using special characters where ISO-8859-1 codepage differs from UTF-8, we've a problem.
When I understand you correct there's a adapter module TextCodepageConversionBean which changes the encoding, right? Then I could use it to encode the inbound ISO-8859-1 message to UTF-8 (which is declaration in XML prolog).
Where can I find more information how to use it? Searching SDN I've just found one other thread where the same module is mentioned, but without further hints.
BR
Holger

New to SOAP - How to create SOAP message for the SOAP described

Hi Friends,
Im bit new to SOAP-JAVA interactions.
I have an SOAP describing
POST /abc/WebSrevices/MyService.asmx HTTP/1.1
Host: 127.0.0.1
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://tempuri.org/BillingAddressValidation"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<BillingAddressValidation xmlns="http://tempuri.org/">
<inXml>string</inXml>
</BillingAddressValidation>
</soap:Body>
</soap:Envelope>
My question is How can I construct an equivalent JAVA message using SAAJ
I wrote like the following
public void performSOAPReadWrite(String transaction){
try{
SOAPConnectionFactory scf = SOAPConnectionFactory. newInstance();
SOAPConnection con = scf.createConnection();
MessageFactory mf =
MessageFactory.newInstance();
SOAPMessage msg = mf.createMessage();
SOAPPart sp = msg.getSOAPPart();
SOAPEnvelope envelope = sp.getEnvelope();
//Adding Content to the Header
envelope.getHeader().detachNode();
SOAPBody body = envelope.getBody();
SOAPElement billingAddressValidation =
body.addChildElement("BillingAddressValidation","http://tempuri.org/");
SOAPElement inXml =
billingAddressValidation.addChildElement("inXml");
inXml.addTextNode(transaction);
URL urlEndpoint = new URL(DEFAULT_SERVER);
// 127.0.0.1/abc/WebSrevices/MyService.asmx
System.out.println("Sending Message");
SOAPMessage reply = con.call(msg,
urlEndpoint);
System.out.println("Reply is "+reply);
}catch (Exception e) {
e.printStackTrace();
// TODO: handle exception
Can any one let me know whats wrong in this ?
Thanx in advance
Im waiting for ur reply
Mahesh Raja Vandyala
Senior Analyst

Hi,
When im running the program I am getting a
javax.xml.soap.SOAPException: Failed to send message:java.io.IOException: The server at http://127.0.0.1/abc/WebSrevices/MyService.asmx returned a 500 error code ( Internal Server Error )
Please ensure that ur URL is correct and the Web service has deployed
This is web service is provided by .net team and im required to take the services of that web service to retrieve some information provided by that.
I can launch the webservice definition thru IE....their they have provide a text box with a Invoke button.
The same data that im sending thru code if invoked thru IE is working fine.
I suspect that the way Im construcint the SOP message is wrong.
Any help in finding out the correctness of the Message in the java code ?
Thanx
Mahesh

Outbound SOAP Message with Attachment

The requirement is to invoke a web service by sending attachments in the outbound SOAP message. The attachment body needs to be assigned in the message flow, using an element E1 extracted from the message incoming into the flow.
I am trying to use attachments variable to set content-type (text/xml) and body using E1. However, these are not getting assigned to attachments variable, as seen by logging the variable.
I was told that $attachments cannot be changed inside the flow (it is marked black in the console unlike the header and body that are marked green). If that is the case, how do we invoke services using attachments from a message flow?
Any pointers would be appreciated.

Hi,
A SOAP message may need to be transmitted together with attachments of various sorts, ranging from facsimile images of legal documents to engineering drawings. Such data are often in some binary format. For example, most images on the Internet are transmitted using either GIF or JPEG data formats. In this document we describe a standard way to associate a SOAP message with one or more attachments in their native format in a multipart MIME structure for transport.
yes it is possible to send attachment with the SOAP.
SOAP Message Packages
A "SOAP message package" contains a primary SOAP 1.1 message. It may also contain additional entities that are not lexically within the SOAP message but are related in some manner. These entities may contain data in formats other than XML. The primary SOAP 1.1 message in a message package may reference the additional entities. Such additional entities are often informally referred to as "attachments." This section describes how to construct SOAP message packages and how SOAP processors will process them.
A SOAP message package is constructed using the Multipart/Related media type, which is defined in RFC 2387. The rules for the construction of SOAP message packages are as follows:
The primary SOAP 1.1 message must be carried in the root body part of the Multipart/Related structure. Consequently the type parameter of the Multipart/Related media header will always equal the Content-Type header for the primary SOAP 1.1 message, i.e., text/xml.
The MIME Multipart/Related encapsulation of a SOAP message is semantically equivalent to a SOAP protocol binding in that the SOAP message itself is not aware that it is being encapsulated. That is, there is nothing in the primary SOAP message proper that indicates that the SOAP message is encapsulated .
For more details you can refer these links
http://www.w3.org/TR/SOAP-attachments
http://www.w3.org/TR/soap12-af/
regards
Aashish Sinha
PS : reward points if helpful

How to view the SOAP message in a web service call + Urgent

Hi All,
Iam trying to test a web service call(Iam using CXF). But I need to view SOAP message sent to web service or need to debug the web service call. Please help me on this regard with example.

Yes. to find any tcp monitor, define a listen port number, task host and port number, changing your request to listen post, then you can monitor TCP/IP like
HTTP/1.1 200 OK
Set-Cookie: JSESSIONID=7A00BD65EF7516AD8947359A25C4D98B; Path=/ComponentName
Content-Type: text/xml;charset=utf-8
Date: Wed, 20 Oct 2004 15:45:03 GMT
Server: Apache-Coyote/1.1
Connection: close
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:testObjectResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:ComponentName">
<testObjectReturn href="#id0"/>
</ns1:testObjectResponse>
<multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:MyObject" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ComponentName">
<name xsi:type="xsd:string">Set Name</name>
<value xsi:type="xsd:string">set Value</value>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
Lixin

Implement a SOAP Request in an SSIS Package that sends a SOAP Message (Env) with Authentication Info, Receives XML FIle?

We need a small SSIS package to pass a SOAP message to a SOAP server and receive the response xml message.
We have the SOAP Endpoint, SOAP Action, and SOAP Message (which contains authentication elements). They work in a Talend Data Integration job (using
Talend's tSOAP component). A screenshot showing the Talend job and the configuration of the tSOAP component
is attached.
We need to implement the same thing in a Microsoft SQL Server 2012 SSIS package but haven't been able to get an SSIS Web Services task to work.
We haven't been able to configure it to pass the SOAP Action and SOAP Message.
How should this be accomplished in SSIS?
kholberger

I guess I was not clear. The Talend job works perfectly (and it took only a few minutes to configure).
I need to replicate the SOAP request function in an SSIS package. I've been trying to configure an SSIS Web Services Task to do that without success.
The SSIS Web Service Task asks for the .wsdl file, which I provide (though the Talend component
does not ask for it), but the SSIS WST does not ask for the SOAP Action or SOAP message. The target web service is protected by a security gateway that rejects the SSIS WST request. Somehow, the Talend tSOAP component sends the
SOAP message, which contains the security definition and authentication credentials (you can see part of that in the screen shot) which the endpoint accepts.
The question is: "How does one implement a SOAP web service request in an SSIS package that sends the SOAP Message".
Thanks.
kholberger

SOAP message format after signing

Experts,
Can any one tell me the format of the soap message after the message is signed with certificate issued by third party?
I am getting signed soap message as follows :
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header>
- <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" SOAP:mustUnderstand="1">
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="sap-6" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">MIIE1TCCA72gAwIBAgICGyQwDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCU0ExDTALBgNVBAoTBFNBTUExGzAZBgNVBAsTElNBTUEgZVRydXN0IENlbnRlcjEfMB0GA1UEAxMWU0FNQSBTdGFnaW5nIFNoYXJlZCBDQTAeFw0wODA5MTYxMDUyNDJaFw0xMDA5MTYxMDUyMzdaMIGUMQswCQYDVQQGEwJTQTEoMCYGA1UEChMfTkNCQiAtIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuazEoMCYGA1UECxMfTkNCQiBXZWIgUmVnaXN0cmF0aW9uIEF1dGhvcml0eTELMAkGA1UECxMCSVQxJDAiBgNVBAMTG2UtZGhxLXMyMDF3ZWIuc2VjLnNlLmNvbS5zYTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA2JDBfb/o41YV7/JOBKa0H/zCIF6Szpn5oEEPjIu63UoD2t3uKZgL0pDpKTrl8hNgSfnbePsn9te0sqmstflIUV8OYv6VCUKIL6ZsxcZliFP7LTWcN7VHa5J80zwJpuZI0lSOTmssRfTczT5wbRiJuf/z/ZUsc9VvP7hMT93Vc0CAwEAAaOCAewwggHoMIIBPAYDVR0gBIIBMzCCAS8wggErBg0rBgEEAYGHHQEBBgUBMIIBGDCB1QYIKwYBBQUHAgIwgcgagcVUaGlzIGNlcnRpZmljYXRlIGhhcyBiZWVuIGlzc3VlZCBieSBTQU1BIGVUcnVzdCBDZW50ZXIgb24gYmVoYWxmIG9mIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuayAoTkNCQikuIE5laXRoZXIgU0FNQSBub3IgTkNCQiBhY2NlcHQgYW55IGxpYWJpbGl0eSBmb3IgYW55IGNsYWltIGV4ZXB0IGFzIGV4cHJlc3NseSBwcm92aWRlZCBpbiB0aGlzIENQLjABggrBgEFBQcCARYyaHR0cDovL3d3dy5lVHJ1c3RjZW50ZXIuY29tLnNhL2RvY3Mvcm9vdGNhX2Nwcy5wZGYwMAYIKwYBBQUHAQEEJDAiMCAGCCsGAQUFBzABhhRodHRwOi8vMTAuMTMxLjEuNjo4MDALBgNVHQ8EBAMCA7gwJwYDVR0lBCAwHgYIKwYBBQUHAwQGCCsGAQUFBwMHBggrBgEFBQcDATAfBgNVHSMEGDAWgBSgYJsSh4qnwzTjhepPMHVJj9ncDAdBgNVHQ4EFgQUXWMeLP/opd8VqdnCf/xSX0/dD8wDQYJKoZIhvcNAQEFBQADggEBAJ2Pjv0V8ke9Vxe4FAOVJ7Hi67STUnad6gIIeT2wTUYwZD9dFf2g4NJnqJ2SF3Q9QKw5rBofU1SjuFw11hnQ3G3UK6Erkn7klS0/vVrAEAg55nzDhYPU3uZyVoobJmtLgNk507U7qkIL86p8tPCDlZoN23od1RG8uAP4K3TyiYgFozVA9tUIUGDDFbqOSACZ6tSrXDzHTfmA2l7zz4tizi/yX57SLjg3kIXKWfwo3nOEJm9xGL/4PyxaXQlNsd3srBrYl9/L78563ExKJ0UvnqKTjvuhRIsm3+E9eFhYAq1Wd/xBIXKPZEK8VwcrEQJqBnEi/2RL0jDULYMR8=</wsse:BinarySecurityToken>
- <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsu-targetID-eed81bc1-2818-11de-a649-000e0cf559d1">
<wsu:Created ValueType="xsd:dateTime">2009-04-13T10:50:41Z</wsu:Created>
<wsu:Expires ValueType="xsd:dateTime">2009-04-13T10:55:41Z</wsu:Expires>
</wsu:Timestamp>
- <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
- <ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
- <ds:Reference URI="#wsuid-body-eed81bc0-2818-11de-cc6a-000e0cf559d1">
- <ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<ds:DigestValue>ybxqsfOoHwh8eItwlr2GgCzrN8Y=</ds:DigestValue>
</ds:Reference>
- <ds:Reference URI="#wsu-targetID-eed81bc1-2818-11de-a649-000e0cf559d1">
- <ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<ds:DigestValue>Kdki/tVoqS6zmkF7x8nA19QouzM=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>a60173OR4QNYvp/0nEFjPaR2wR6glTj1FQO31YNGn0NR5XKuB2Ye3dfsfwfB6bdDEmXwvOcEfNln grH7hjoItDC1z8luCpXjs7Gy2viF4XCOdgqxC6MnFOwdZpKodrjESYTjzsNUiXcHUEntGzv4Ry8U zCEw9lLT7koAcTXk/NM=</ds:SignatureValue>
- <ds:KeyInfo>
- <wsse:SecurityTokenReference>
<wsse:Reference URI="#sap-6" />
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="sap-6" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">MIIE1TCCA72gAwIBAgICGyQwDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCU0ExDTALBgNVBAoTBFNBTUExGzAZBgNVBAsTElNBTUEgZVRydXN0IENlbnRlcjEfMB0GA1UEAxMWU0FNQSBTdGFnaW5nIFNoYXJlZCBDQTAeFw0wODA5MTYxMDUyNDJaFw0xMDA5MTYxMDUyMzdaMIGUMQswCQYDVQQGEwJTQTEoMCYGA1UEChMfTkNCQiAtIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuazEoMCYGA1UECxMfTkNCQiBXZWIgUmVnaXN0cmF0aW9uIEF1dGhvcml0eTELMAkGA1UECxMCSVQxJDAiBgNVBAMTG2UtZGhxLXMyMDF3ZWIuc2VjLnNlLmNvbS5zYTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA2JDBfb/o41YV7/JOBKa0H/zCIF6Szpn5oEEPjIu63UoD2t3uKZgL0pDpKTrl8hNgSfnbePsn9te0sqmstflIUV8OYv6VCUKIL6ZsxcZliFP7LTWcN7VHa5J80zwJpuZI0lSOTmssRfTczT5wbRiJuf/z/ZUsc9VvP7hMT93Vc0CAwEAAaOCAewwggHoMIIBPAYDVR0gBIIBMzCCAS8wggErBg0rBgEEAYGHHQEBBgUBMIIBGDCB1QYIKwYBBQUHAgIwgcgagcVUaGlzIGNlcnRpZmljYXRlIGhhcyBiZWVuIGlzc3VlZCBieSBTQU1BIGVUcnVzdCBDZW50ZXIgb24gYmVoYWxmIG9mIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuayAoTkNCQikuIE5laXRoZXIgU0FNQSBub3IgTkNCQiBhY2NlcHQgYW55IGxpYWJpbGl0eSBmb3IgYW55IGNsYWltIGV4ZXB0IGFzIGV4cHJlc3NseSBwcm92aWRlZCBpbiB0aGlzIENQLjABggrBgEFBQcCARYyaHR0cDovL3d3dy5lVHJ1c3RjZW50ZXIuY29tLnNhL2RvY3Mvcm9vdGNhX2Nwcy5wZGYwMAYIKwYBBQUHAQEEJDAiMCAGCCsGAQUFBzABhhRodHRwOi8vMTAuMTMxLjEuNjo4MDALBgNVHQ8EBAMCA7gwJwYDVR0lBCAwHgYIKwYBBQUHAwQGCCsGAQUFBwMHBggrBgEFBQcDATAfBgNVHSMEGDAWgBSgYJsSh4qnwzTjhepPMHVJj9ncDAdBgNVHQ4EFgQUXWMeLP/opd8VqdnCf/xSX0/dD8wDQYJKoZIhvcNAQEFBQADggEBAJ2Pjv0V8ke9Vxe4FAOVJ7Hi67STUnad6gIIeT2wTUYwZD9dFf2g4NJnqJ2SF3Q9QKw5rBofU1SjuFw11hnQ3G3UK6Erkn7klS0/vVrAEAg55nzDhYPU3uZyVoobJmtLgNk507U7qkIL86p8tPCDlZoN23od1RG8uAP4K3TyiYgFozVA9tUIUGDDFbqOSACZ6tSrXDzHTfmA2l7zz4tizi/yX57SLjg3kIXKWfwo3nOEJm9xGL/4PyxaXQlNsd3srBrYl9/L78563ExKJ0UvnqKTjvuhRIsm3+E9eFhYAq1Wd/xBIXKPZEK8VwcrEQJqBnEi/2RL0jDULYMR8=</wsse:BinarySecurityToken>
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="sap-6" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">MIIE1TCCA72gAwIBAgICGyQwDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCU0ExDTALBgNVBAoTBFNBTUExGzAZBgNVBAsTElNBTUEgZVRydXN0IENlbnRlcjEfMB0GA1UEAxMWU0FNQSBTdGFnaW5nIFNoYXJlZCBDQTAeFw0wODA5MTYxMDUyNDJaFw0xMDA5MTYxMDUyMzdaMIGUMQswCQYDVQQGEwJTQTEoMCYGA1UEChMfTkNCQiAtIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuazEoMCYGA1UECxMfTkNCQiBXZWIgUmVnaXN0cmF0aW9uIEF1dGhvcml0eTELMAkGA1UECxMCSVQxJDAiBgNVBAMTG2UtZGhxLXMyMDF3ZWIuc2VjLnNlLmNvbS5zYTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA2JDBfb/o41YV7/JOBKa0H/zCIF6Szpn5oEEPjIu63UoD2t3uKZgL0pDpKTrl8hNgSfnbePsn9te0sqmstflIUV8OYv6VCUKIL6ZsxcZliFP7LTWcN7VHa5J80zwJpuZI0lSOTmssRfTczT5wbRiJuf/z/ZUsc9VvP7hMT93Vc0CAwEAAaOCAewwggHoMIIBPAYDVR0gBIIBMzCCAS8wggErBg0rBgEEAYGHHQEBBgUBMIIBGDCB1QYIKwYBBQUHAgIwgcgagcVUaGlzIGNlcnRpZmljYXRlIGhhcyBiZWVuIGlzc3VlZCBieSBTQU1BIGVUcnVzdCBDZW50ZXIgb24gYmVoYWxmIG9mIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuayAoTkNCQikuIE5laXRoZXIgU0FNQSBub3IgTkNCQiBhY2NlcHQgYW55IGxpYWJpbGl0eSBmb3IgYW55IGNsYWltIGV4ZXB0IGFzIGV4cHJlc3NseSBwcm92aWRlZCBpbiB0aGlzIENQLjABggrBgEFBQcCARYyaHR0cDovL3d3dy5lVHJ1c3RjZW50ZXIuY29tLnNhL2RvY3Mvcm9vdGNhX2Nwcy5wZGYwMAYIKwYBBQUHAQEEJDAiMCAGCCsGAQUFBzABhhRodHRwOi8vMTAuMTMxLjEuNjo4MDALBgNVHQ8EBAMCA7gwJwYDVR0lBCAwHgYIKwYBBQUHAwQGCCsGAQUFBwMHBggrBgEFBQcDATAfBgNVHSMEGDAWgBSgYJsSh4qnwzTjhepPMHVJj9ncDAdBgNVHQ4EFgQUXWMeLP/opd8VqdnCf/xSX0/dD8wDQYJKoZIhvcNAQEFBQADggEBAJ2Pjv0V8ke9Vxe4FAOVJ7Hi67STUnad6gIIeT2wTUYwZD9dFf2g4NJnqJ2SF3Q9QKw5rBofU1SjuFw11hnQ3G3UK6Erkn7klS0/vVrAEAg55nzDhYPU3uZyVoobJmtLgNk507U7qkIL86p8tPCDlZoN23od1RG8uAP4K3TyiYgFozVA9tUIUGDDFbqOSACZ6tSrXDzHTfmA2l7zz4tizi/yX57SLjg3kIXKWfwo3nOEJm9xGL/4PyxaXQlNsd3srBrYl9/L78563ExKJ0UvnqKTjvuhRIsm3+E9eFhYAq1Wd/xBIXKPZEK8VwcrEQJqBnEi/2RL0jDULYMR8=</wsse:BinarySecurityToken>
</wsse:Security>
</SOAP:Header>
- <SOAP:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-body-eed81bc0-2818-11de-cc6a-000e0cf559d1">
- <ns0:MasterData xmlns:ns0="http://s24dh043/SA2SEC/WSD/SATOSEC">
- <MasterData_Input>
<PARTNER_ID>XYZ</PARTNER_ID>
</MasterData_Input>
</ns0:MasterData>
</SOAP:Body>
</SOAP:Envelope>
In the above soap envelope tag "BinarySecurityToken" repeated thrice. So is it the standard method or I am missing any configuration. Becacuse our partner(webmethods) understands only one occurance of "BinarySecurityToken" in soap message.
Edited by: Santhosh on Apr 13, 2009 1:42 PM

Hi ,
Just a few pointers:
"Element caching should not be used at the top levels of an XML document by a generic encoder, since it is
unlikely that the full document would be repeated. With SOAP, it is typically wise to start element caching at the
third level, i.e. leave Envelope and Body alone. Of course, if the encoder has more knowledge of the messages
sent, going further up may pay off."
regards
joel

I need to secure SOAP message sent into SOAP adapter, how to?

Similar Messages

Maybe you are looking for