mendelson opensource OFTP2

In reply to Problem with verification of digital signature (message-digest attribute does not match...) jfv, the AS2 messages are embedded in MIME messages and sent via HTTP. A single byte that has been modified in the whole transmission will result ... [More] in such an error. If you dont have both systems in your hand and could clarify bytewise what happens there it is hard to find the reason... Regards Log in or register to post comments [Less]

In reply to jfv, Thanks for your reply... I deactivated the "request signed MDN" > still the same issue. Problem occurs when the partner sends me the message. Decryption is OK, but when m-e-c wants to verify the signature, it gives the error ... [More] "Verification of digital signature failed message-digest attribute value does not match calculated value". But I'm wondering... when I send a message, I receive a signed MDN from the counterparty. And this signed MDN is verified OK... Is this the same process when you verify a signature for a MDN and for a message? Thanks a lot. Kind regards, JF Log in or register to post comments [Less]

In reply to Problem with verification of digital signature (message-digest attribute does not match...) jfv, hard to say how to help out regarding this issue. Perhaps just switch off the "request signed mdn" for this partner. Regards Log in or register to post comments

Hi all, a new version of the community version of the mendelson AS2 software has been released. You could download your version at http://as2.mendelson-e-c.com Enhancement: *mendelson opensource AS2 contains certificate manager for ... [More] SSL/encryption/signature now - it is no longer needed to edit the underlaying keystores using a third party tool like portecle *Impoved the community versions documentation *The user interface (security tab) contains a hint now that the mendelson AS2 will never change a keystore password - these settings are just to work with keystores that have been edited using thried party tools Updates: *Update to BC 1.50 (crypto API) *Update to HSQLDB 2.3.2 (Database) Hint: The mendelson opensource AS2 will run fine with Java 64 bit VMs. If you have problems with the memory consumption please install a 64 bit java VM (not included), patch the VM with the "jurisdiction policy strength files" (Oracle download) and set the main memory of the JVM to 4 GB. Please have a look at the included file "upgrade_howto.txt", it explains how to upgrade from an older version of mendelson opensource AS2. --- Thank you all for your feedback and your help Your mendelson dev team Forum: AS2 [Less]

In reply to OFTP2 directory polling issue? lancasm, please contact the mendelson email support if you are using a commercial version of mendelson AS2. Regards Log in or register to post comments

In reply to jfv, Thanks... Changing this did not resolve the problem, unfortunately. I'm using the latest version of m-e-c (at least the one supporting SHA-2 certificates). When I send a message to the partner, the MDN comes back, signed by the ... [More] partner, and signature is valid. When the partner sends me a message, message is decrypted ok but signature cannot be verified > "Verification of digital signature failed message-digest attribute does not match calculated value". I asked the counterparty to setup the "Content Transfer Encoding" to "Binary" but this doesn't seem to be so straightforward for him to do this... I'll keep you informed once he has done this, if this helped. Any suggestion in the meanwhile would be highly appreciated :-) Kind regards, JF Log in or register to post comments [Less]

In reply to OFTP2 directory polling issue? Additional information: After re-reading my post, it's probably worth mentioning that the [user_defined_id] portion of the file name is a unique reference for the file being transmitted, so no two files will ever have the same name. Log in or register to post comments

Hi, We currently use a licenced version of Mendelson OFTP2 to send files to a customer. We move the files into the outbound folder and usually they get sent out without any issues. Sometimes, if there are several files to be transmitted, not all of ... [More] them will be transmitted. It looks like there may be an issue with the process that polls the outbound folder. I use the following VBScript code to load the files into the folder: MyResult = OFTP2Route(WScript.Arguments(0), WScript.Arguments(1), WScript.Arguments(2), WScript.Arguments(3)) WScript.Quit(MyResult) Function OFTP2Route(Destination, filePathAndName, UserDefinedID, VirtualFileName) on error resume next Set objFSO = CreateObject("Scripting.FileSystemObject") NewName=Destination & "^" & VirtualFileName & "^" & UserDefinedID objFSO.movefile filePathAndName,"D:\Program Files\OFTP2\Outbound\" & NewName set f=objFSO.GetFile("D:\Program Files\OFTP2\Outbound\" & NewName) if err then wscript.echo err.description OFTP2Route=1 else wscript.echo "File " & UserDefinedID & " queued for delivery to " & Destination OFTP2Route=0 end if set f=nothing set objFSO=nothing End Function To paraphrase what it does, the file is moved into the Outbound folder using a file name in [destination]^[virtual_file_name]^[user_defined_id] format. The script then attempts to use the filesystemobject.getfile to get a reference to the moved file. If an error occurs when it does this, the error message will be outputted otherwise the script will output a message reporting that the file has been successfully queued for delivery to it's destination. In all cases, the script reports no error, so I can be confident that the files are being successfully moved to the outbound folder. Within a few minutes, the Mendelson OFTP2 software would detect the files and send them out. I have tracing switched on, and this has allowed me to see that on occasion, no attempt is being made to send out some of the files. Resubmitting the same files shortly afterwards resolves the problem and they get transmitted successfully. As a short-term solution, I have a scheduled task processing the trace files in order to detect and resubmit any files which failed to go out. Obviously this is not a good long-term solution. I would like to know if this is a known issue, and if so, whether or not a fix is available. I'd be more than happy to provide any additional information if you should need it. The version of the software we're using is "OFTP2 2012 build 83". Thanks and best regards, Mark. Forum: Global [Less]

In our office we have a corporate proxy and any external communication goes through it. This isn't a problem using Mendelson v39, just need to configure the proxy parameters in Preferences and it works perfectly. But to my surprise when I use ... [More] Mendelson v41 and v43 the messages can't go through the proxy anymore. Debugging the code I can see Mendelson tries to send the message, the proxy sends back an "authorization required", but then when Mendelson tries to resend it an exception is thrown because the Entity is not readable again. I've looked for changes in the code in those versions but couldn't find anything, do you have a clue on how I could solve this? I'm testing with equally configured v39, v41 and 43 on the same computer. This is the exception I get:org.apache.http.client.NonRepeatableRequestException: Cannot retry request with a non-repeatable request entity. This is the line from where I get the exception in MessageHttpUploader.performUpload():HttpResponse httpResponse = httpClient.execute(targetHost, filePost, localcontext); This is the associated relevant log: - Sending AS2 message to http://testas2.mendelson-e-c.com:8080/as2/HttpReceiver, sync MDN requested. - Using proxy XX.XX.XX.XX:8012. - MessageHTTPUploader.performUpload: [ClientProtocolException] Forum: AS2 [Less]

Hello, I solved below issue last week. http://community.mendelson-e-c.com/node/2831 But I facing another problem. Now we can send EDI message through the gateway(GXS) to JLR. But, when GXS or JLR send EDI message to our OFTP2 server, they got the ... [More] below error message. --------------------- start of message ------------------------- 074733 FTP0220I 00 Initiating a session with O2011PHACZECH 074735 NSS6118E 00 Received unexpected server certificate : 074735 NSS6119I 00 Server certificate - 074735 NSS6120I 00 Issuer = /C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=Terms of use at https://www.verisign.com/rpa (c)10/CN=VeriSign Class 3 International Server CA - G3 074735 NSS6121I 00 Wanted certificate - 074735 NSS6122I 00 Issuer = /C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=Terms of use at https://www.verisign.com/rpa (c)10/CN=VeriSign Class 3 International Server CA - G3 074735 NSS6123I 00 File = /opt/msggwy/Odex/client_certs/O2011PHACZECH.pem 074735 FTP0301I 00 Remote has disconnected from line 074735 FTP0301I DTE Clearing - No additional information 074735 FTP0309I 00 Session cleanup complete --------------------- end of message ------------------------- JLR and GXS said our certificate was wrong. But now we using same certificate with another customer. What was wrong? How can I solve this problem? I really confused now. Also, here I attached our systemactivity log. Please help me. Forum: OFTP2 AttachmentSize systemactivity.txt24.13 KB [Less]