Signed XML in SOAP Adapter

Hello Experts,
I have a scenario with receiver SOAP adapter, I have used the security profile in the channel and receiver agreement i have selected sign and all rudimentary requirements..
But im unable to see the signed payload in the CC monitoring..it should be in the format
<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:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="................</wsse:BinarySecurityToken>
<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="#id-24819136">
<ds:Transforms>
<ds:Transform Algorithm=...........
Im not able to see it in the SOAP adapter...have i missed something in the config...I have generated the cert in visual admin and given the correct values too in the channel and recv agreement.
Can ne one elucidate on this please...
How can i view the signed xml coming from the SOAP adapter?
Regards,
Farooq
Edited by: Farooq Hussain on Nov 12, 2008 7:46 PM

Hi Farooq
You have generated certificates? this will encrypt complete xml while sending. for that you need to set procedure as Encrypt this is what my understanding in this.
XML Signature
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/55814003-0b01-0010-1ca2-c683a191ebfc
Did you have checked with this
Using Digital Signatures in XI
it doesn't talk about generating the certificate and encrypting complete message but it actually encrypt complete message when you generate certificate.
How XML Encryption can be done using web services security in SAP NetWeaver XI
This also speaks similar. I am not able to get the link .. try search for "Ensure the Confidentiality of Your SOAP Message Content" to understand more on this
Thanks
Gaurav

Similar Messages

NullPointerException while sending signed XML via SOAP to Axis webservice

Hello,
I was wondering if it was possible to change the behavior of Apache XML Security libraries and delete "ds:" namespaces while digitally signing XML files.
We are trying to send signed XML to a local chilean IRS, as a part of an automatic autentication process. The steps to authenticate are quite straightforward and involve:
1. Obtain from webservice 1 a "seed", which is a random number representing temporal session opened
2. Sign this seed (in XML format) using our certificate
3. Send signed XML to another webservice 2, which should validate it and open a permanent session, returning a "token", which is an alphanumeric string
What happens is that steps 1 and 2 are completed without problems, while we cannot pass step 3. The webservice (as far I know mounted on Apache Axis) fails with ugly error "NullPointerException".
The IRS says that our signed XML, although valid, seems strange to them, as it contains those "ds:" added by Apache Xml Security libraries while signing the file.
So here comes the question: is it possible to obtain valid signed XML without those "ds:"? What other reasons may result in that NullPointerException error?
We use simple Java class and VeriSign certificate stored in Java keystore to sign XML files, and Apache Xml Security 1.2.0 jars.
For any clues that could help us thank you in advance.
Jack

Hi,
Few months ago we had also problems with "locked user" in XI, in our case XIAPPLUSER was sometimes (b)locked.
Perhaps note:
721548 Changing the passwords of the XI 3.0 service users
will help you.
We removed and entered the service users again, with the password in CAPITALS and language blank.
After that our problem was solved, I hope yours too.
Regards
Jack

Prolog with soap adapter in PI

Dear All,
We run a scenario Proxy=>PI=>HTTP
The remote service accepts messages POSTed using either the form-encoded format (name, value pairs)
or the multi-part mime format which enables the files to be passed to the web service.
In both cases, the external service replies with a multi-part message.
We are going to use the SOAP adapter (plain HTTP does not support attachments)
with nosoap flagged.
What is best approach to add a prolog before the actual XML with SOAP adapter,
to simulate the form-encoded format?
Example :
USER=USER1&PASS=PASS1&DB=DB1
In the 2nd situation, how to create the different documents before the actual XML?
Example :
7d924f5b0464
Content-Disposition: form-data; name="USER"
USER1
7d924f5b0464
Content-Disposition: form-data; name="PASS"
PASS1
7d924f5b0464
Content-Disposition: form-data; name="DB"
DB1
Best regards,
KR,
Laurent

Dear All,
We run a scenario Proxy=>PI=>HTTP
The remote service accepts messages POSTed using either the form-encoded format (name, value pairs)
or the multi-part mime format which enables the files to be passed to the web service.
In both cases, the external service replies with a multi-part message.
We are going to use the SOAP adapter (plain HTTP does not support attachments)
with nosoap flagged.
What is best approach to add a prolog before the actual XML with SOAP adapter,
to simulate the form-encoded format?
Example :
USER=USER1&PASS=PASS1&DB=DB1
In the 2nd situation, how to create the different documents before the actual XML?
Example :
7d924f5b0464
Content-Disposition: form-data; name="USER"
USER1
7d924f5b0464
Content-Disposition: form-data; name="PASS"
PASS1
7d924f5b0464
Content-Disposition: form-data; name="DB"
DB1
Best regards,
KR,
Laurent

Javax.xml.rpc.soap.SOAPFaultException +HttpBinding Adapter 11g

Hi all,
when i am trying to use HttpBinding Adapter with Type= 'Service' , Verb='POST' ,*Operation Type='Request-Response'* , after these settings when i deploy my application on Enterprise Manager than my operation works fine but i get following error in log file.
Please suggest me what am i doing wrong...................
<javax.xml.rpc.soap.SOAPFaultException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
 at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.generateSoapFaultException(WebServiceEntryBindingComponent.java:1052)
 at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.processIncomingMessage(WebServiceEntryBindingComponent.java:889)
 at oracle.integration.platform.blocks.soap.FabricProvider.processMessage(FabricProvider.java:113)
 at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
 at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1081)
 at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:581)
 at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:232)
 at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:192)
 at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:484)
 at oracle.integration.platform.blocks.soap.FabricProviderServlet.doPost(FabricProviderServlet.java:507)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Edited by: 835461 on Jul 19, 2011 4:07 AM

This operation is assyncronous ?

XI Soap Adapter: problems in parsing XML

Hallo,
I call a Web Service using XMLSpy and this is the response (note tag <File>):
 <SOAPSDK4:ExpBaselineResponse xmlns:SOAPSDK4="http://tempuri.org/PRWBS_PRIMAVERA/message/">
 <RESULT>OK</RESULT>
 <File><?xml version='1.0' encoding='UTF-8'?>
<Dati:Parametri xmlns:Dati="Schema">
 <ELSAG xmlns="Schema">
 <proj_id>4623</proj_id>
 <BS_short_name>FS0084AAAA01 - B1</BS_short_name>
 <BS_proj_id>1302</BS_proj_id>
 <TARGET_START>2004-04-01</TARGET_START>
....etc...
If I call the same Web Service from XI, this is the response:
<SOAPSDK4:ExpBaselineResponse xmlns:SOAPSDK4="http://tempuri.org/PRWBS_PRIMAVERA/message/" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAPSDK3="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAPSDK2="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAPSDK1="http://www.w3.org/2001/XMLSchema">
 <RESULT>OK</RESULT>
 <File><?xml version="1.0" standalone="yes"?>
<Dati:Parametri xmlns:Dati="Schema">
 <ELSAG xmlns="Schema">
 <proj_id>4623</proj_id>
 <BS_short_name>FS0084AAAA01 - B1</BS_short_name>
 <BS_proj_id>1302</BS_proj_id>
 <TARGET_START>2004-04-01</TARGET_START>
....etc....
In my flow, I use a java mapping to parse the content of tag <File> into a message.
My mapping works correctly only with the first option.
Is it possible to change XI Soap Adapter encoding for HTML?
My java mapping uses this parser:
 public void execute(InputStream MyInputStream, OutputStream MyOutputStream)
 throws StreamTransformationException {
 SAXReader reader = new SAXReader();
 Document document;
 try {
 document = reader.read(MyInputStream);
this instruction generates an Exception only with XI message.
Can anybody help me??
Thanks;-)

Hi,
I would suggest you go through this Pdf for the SOAP Adapter configuration:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40728f7b-0401-0010-d9bc-8c73884a3789
And also have a glance on the info for webservices given below,
Just go through these links and they will surely help you learn more about Webservices:
<a href="/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi Webservices using SAPXI</a>
<a href="/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies between SAP System & Webservice Using Proxies</a>
You can Go through these links to get some info about accessing Webservices:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/f9bc3d52f39d33e10000000a11405a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/b7/d7baaf1481a349ab723e3acd7334b3/content.htm
Go through these links which will surely help you find an answer to your problem.....
Regards,
Abhy

Error in SOAP Adapter because XML is big

Hi guys! I have a SOAP Adapter (Sender) that works fine when the XML it receives is small. If the XML is big, this error happens: 
java.lang.NullPointerException; nested exception caused by:
java.lang.NullPointerException; nested exception caused by:
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)
 at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 at javax.xml.parsers.SAXParser.parse(Unknown Source)
 at javax.xml.parsers.SAXParser.parse(Unknown Source)
 at com.sap.aii.messaging.util.StreamXMLScannerImpl$EventProducer.run(StreamXMLScannerImpl.java:598)
 at java.lang.Throwable.<init>(Throwable.java:56)
 at java.lang.Throwable.<init>(Throwable.java:67)
 at org.xml.sax.SAXException.<init>(Unknown Source)
 at org.xml.sax.SAXParseException.<init>(Unknown Source)
 at com.sap.engine.lib.xml.parser.NestedSAXParseException.<init>(NestedSAXParseException.java:23)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
 at javax.xml.parsers.SAXParser.parse(Unknown Source)
 at javax.xml.parsers.SAXParser.parse(Unknown Source)
 at com.sap.aii.messaging.util.StreamXMLScannerImpl$EventProducer.run(StreamXMLScannerImpl.java:598)
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)
 at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 3 more
 
ps: the big XML is well formed! It seems the application server refuses the http request (the message does not appear at SXMB_MONI) 
thanks in advance 
Julio

Julio,
Are you sure that XML is correct?
No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)
I also see Parse exceptions at different lines?
check the NOTE : 931765 @
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=931765
Check if the incoming XML has style informaton associated with it. Refer to following link for more info.
http://schemas.xmlsoap.org/soap/envelope/
If the problem still persists, Restart J2EE Instance.
Regards,
Venkat.
Edited by: Venkat Anusuri on Jun 3, 2009 5:34 PM

Send and Receive an xml file over SOAP adapter

hi,
I want to send an xml file as an attachment over SOAP adapter and Response also should be file.
Can anybody tell the exact solution.
Useful responses will be appreciated
Thanks
Jaideep Jain

Hi Jaideep,
Yes you can send the any file throgh SOAP adapter by selecting the Keep Attachments option.
For your requirement you can go throgh the following link
Re: Attachments in SOAP adapter
http://www.w3.org/TR/SOAP-attachments
http://www.theserverside.com/tt/articles/article.tss?l=SendingAttachmentsWithSOAP
Regards
Sridhar Goli

Soap - Adapter / XML-Handling

Hello @,
is it possible to receive a xml-file via SOAP-Adapter and pass it to a another SOAP-Receiver without haveing any mapping between?

>
Bernd Kresse wrote:
> Ah ... ok, that is also my knowledge about this. I must define the structure of the message to handle a message, regardless of needing a mapping.
>
> What about define a "structure" with only tag and put the "real" structure in this single tag?
if you are not using a mapping then the structure is irrelevant (for file scenarios etc) but since yours is a SOAP the structure will anyway be present in terms of a WSDL

SIGNING problem in soap receiver adapter

Dear Friends,
I am sending the file to soap adapter , it reaching to reciever system but I SIGNING is not happening.
sender side file adapter
receiver side soap adapter
sender side ok , reciever side also ok but only the problem is SIGNING.
receiver side any settings are required.
Please suggest me how to resolve this issue.
Regards,
Shalini Shah

Hi,
If you want to sign the message then enable webservice security in receiver communication channel and specify the certficate for signing in the receiver agreement. Certificates need to be created in Visual Admin and corresponding public key should be provided to the partner for validating the signature.
You need to create a connection type G in SM59 which is required for connecting to J2EE from integration server and you need to specify this connection in the port which need to be created in tcode lpconfig.
Regards,
Prakash

SOAP Adapter without SOAP envelope sets contenttype to application/xml

Hi,
I wrote a adaptermodul for the SOAP adapter to create a SOAP:HEADER.
I disable the SOAP envelope in the communication channel.
Now I get a error from the WebService Provider because the SOAP Adapter sends with Content-Type application/xml and not text/xml. I set the content-type in the adapter module but it seens to not work.
How can I correct this ?
Regards,
Gerald

Hi
Simple answer is NO, it is not possible (without party/channel/ service etc to process the request)
but it is worth a try to check if the URL encoding works.. though I have not tried..
for example sending the hex value of the "?" - %3F%
URL is a generic topic, you can search that to get more information
(ex : http://www.blooberry.com/indexdot/html/topics/urlencoding.htm)
Regards
Vishnu

Security Issues: SSL on SOAP Adapter and Digital Signature in BPM

Hi there,
we're developing a R/3-XI-3rd Party Application scenario, where the XI/3rd Party communication is based on a webservice (SOAP adapter with SSL). Also, the messages in the XI/3rd Party communication must be digitally signed. I've got some questions on both subjects.
1. About the SSL. I've started to investigate what will be necessary to enable the HTTPS option under SOAP Adapter (it's not enabled now). If I'm not correct, all I need to do is:
- check whether the SAP Java Crypto Lib is installed in the Web AS;
- generate the certificate request in the Visual Administrator and, after acquiring the certificate, store it with the KeyStorage option.
Is that right?
I'm considering that I won't need to use SSL in the ABAP Web AS, only the J2EE Java Engine (since the SOAP Adapter is based on J2EE).
2. About the digital signature. As a first solution, we had decided on accessing a webservice based on another machine running a signature application. We'd send the unsigned XML and receive a signed XML. But since that needed to be done into the BPM, I thought that using a piece of Java code in a mapping would suit it better.
But to be able to use the hashing/encrypting/encoding algorithms, which library needs to be installed? Is it the same SAP Java Crypto Lib that was installed for the SSL enabling?
Thanks in advance!

Hello Henrique,
1. You're right. For detailed instructions please have a look at the online help: http://help.sap.com/nw04 - Security - Network and Transport Layer Security - Transport Layer Security on the SAP J2EE Engine
2. The SOAP adapter supports security profiles. Please have a look at the online docu http://help.sap.com/nw04 -Process Integration - SAP Exchange Infrastructure - Runtime - Connectivty - Adapters - SOPA Adapter - Configuring the Sender SOAP adapter and from the link under Security Parameters to the Sender Agreement. You'll find some additional information in the following document: http://service.sap.com/~sapdownload/011000358700002767992005E/HowToMLSXI30_02_final.pdf
Rgds.,
Andreas

SOAP adapter URL causing problems

Hi gurus,
As of PI 7.1, SAP is recommending to use:
http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace
instead of
http://<serverhost>:<port>/XISOAPAdapter/MessageServlet?channel=<party>:<ServiceName>:<ChannelName>
while sending messages to the SOAP adapter. BUT, the new format is causing problems when the developers are trying to import the WSDL (to Webdynpro, eclipse, etc). Also, XMLSpy complains that the xml is not well-formed because of the soap address field.
So I removed the & signs and replaced them with the escape equivalent of & for the new format and tried to use:
http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace
But this time, SOAP adapter replies saying there is no binding. How to overcome this?
Thanks
Gokhan

try this format:
http://<hostname OR IP addr>:<portno>/XISOAPAdapter/MessageServlet?channel=:<SenderService>:<SenderSOAPCC>&version=3.0&Sender.Service=<senderService>&Interface=<senderNamespace>%5E<senderMI>

Soap adapter default encoding

Hi there,
we have a XI <-> webservice scenario, where the XML messages are sent in a string (the wsdl is wrapped, literal) with digital signing.
As of now, we have a problem in the digital signing, since the webservice won't validate the signature. We made some tests and this is what I've concluded.
From what I've observed, there are three ways of sending XML file content in a string (let me know if there are more). They are:
1. putting the xml content between "<![CDATA[" and "]]>";
2. replacing '<', '>' and '"' with "<", ">" and """;
3. replacing '<' and '>' with "<" and ">".
2 and 3 appear to be different encodings.
We tried to send three messages to a test webservice, each with a different way of defining the string, using receiver soap adapter. This test webservice was located in a local machine and we ran a sniffer on it. The three incoming messages were logged by the sniffer, but the upseting news were that the three of them had the same encoding in the input string, which was the third one above ("<" and ">", which by the way is the default by UTF-8).
This only occurs when using SOAP adapter. I tested File adapter and it sent the file exactly how delivered by the sender service (meaning, with the different encodes or with CDATA). We even thought about using module processor for replacing the characters in the message, but since any custom module processor comes before the main adapter module processor, it won't have any effect on the final message.
Using XMLSpy, I sent some test messages to our digital signer (which is also a webservice) with the three ways and it returned a different output when using "<" encoding in the input. Then, I sent this signed message to the webservice and it validated the signature!
We are suspecting that the webserver (which is IBM's WebSphere) always converts the input string to "<", and when they calculate the message hash code, it's different from what we sent (since we always sign a "<" encoded message).
My question is: is there any way of changing the default encode that the soap adapter module processor uses? Or at least of making it not changing the encode of the payload? If it were possible, we would send the message to the signer webservice with "<" encoding and the problem would be solved.
Thanks in advance,
Henrique.

Morten,
actually, we've found out that < = < , in both UTF-8 and ISO-8859-1 encodings. It makes no difference if you use one or the other.
The point which was troublesome for us were the special characters (like á,â,à,ã,é, etc) which have different encoding for UTF-8 and ISO-8859-1. Since we had identified that the service we were accessing wasn't able to identify these characters properly, we just removed them from the string fields and that worked out for us.
Hope it helps you out.
Regards,
Henrique.

Base64 encoding in SOAP adapter

Hi,
Is it possible to transform outgoing messages to Base64 encoding format in XI using module processors and security encryption? I'm using receiver SOAP adapter (without SOAP header) and using PayloadZipBean module processor to zip the outgoing message. Also I need to add digital signature and base64 encryption to the zipped message. Please let me know how this can be achieved.
Thanks,
Dipankar

hi dipankar
check the below blog
How to use Digital Certificates for Signing & Encrypting Messages in XI
How to use Digital Certificates for Signing & Encrypting Messages in XI
hope this resolves your issue
additionally check this
How to use Client Authentication with SOAP Adapter
How to use Client Authentication with SOAP Adapter
also
How XML Encryption can be done using web services security in SAP NetWeaver XI
How XML Encryption can be done using web services security in SAP NetWeaver XI
reward points if helpfull
regards
kummari
Edited by: kummari on Jul 19, 2008 7:24 AM

Which Adapter to use - HTTP or SOAP Adapter?

Hi Experts,
The third party system will be sending a standard HTTP request with a standard SOAP envelope containing standard XML.
So in this case what adapter I should use HTTP or SOAP?
What is the difference between these two adapters and in which scenarios this should be used?
Thanks.

Hi,
The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data using a plain HTTP connection. Depending on the receiver system, outbound messages can be enhanced with certain information.
The SOAP adapter enables you to exchange SOAP messages between remote clients or Web service
servers and the Integration Server or the PCK.
In the SOAP adapter, you can specify security settings to be used to sign/verify the SOAP body.
In addition, you can specify the standard to be used for signing/verifying the SOAP message
whenever Xi need to communicate with any sort of webservice i.e remote applications it uses SOAP adapter..
And XI uses HTTP adapter when you want to post a HTTP request message from a web application to XI.
HTTP Adapter :
1) HTTP Adapter is used by extenal systems to connect to Intergartin server using native HTTP Interface
2) http adapter is a service which is directly connected to integration engine
SOAP Adapter :
1)Allows Local Processing in AAE
2)Exaclty One Operation per Interface
3)Modules for Receiver Adapter
With regards,
Pinangshuk.

Signed XML in SOAP Adapter

Similar Messages

Maybe you are looking for