RMG
The sender sends it from a java program.
I am the receiver. I receive the data as xml node. The content type is verified to be text/xml
These are the steps that I perform when I receive the xml node
a) pub.xml: xmlNodeToDocument
b) pub.xml:documentToXMLString
c) pub.xml:queryXMLNode - extract the signature and signed msg from the xml
d) pub.string:base64Decode - signatue
e) pub.string:stringToBytes - convert the body into bytes
f) pub.security.pkcs7:verify - the signature
The update: Now the client deliberately gave ‘\r\n’ after each tag and I can verify it correctly when I get it from the file they send me, but my service still fails and I could see there are space characters in the xml. Now if I manually remove space characters the verification will pass, what could be done on the client side since I have other working clients (dotNet) here.
Original Msg Tried from the input file that they provided (with new line chars inserted by client)
The same message received over https (spaces can be seen marked, notice spaces after \r\n)
Part of various trials I asked them to send the data zipped and streamed and found that it was untampered and verifiable when unzipped from my side.
Tong
These are the steps that I always used to verify the signature. How could I get the signature and the signed body from the xml without parsing.?
Thahir
#webMethods#Integration-Server-and-ESB#Flow-and-Java-services