mendelson opensource OFTP2

Hi all, a new version of the community version of the mendelson OFTP2 software has been released. You could download your version at http://oftp2.mendelson-e-c.com Enhancement: *It's possible to clone an existing partner in the partner management now ... [More] *A new option has been added to forbid partners to route via the local station *The possibility to add a connection test has been added to the partner settings. If the related port uses SSL the remote certificate is shown. If the partner uses SSL Client Authentication (which is conditional) the connection test will fail *The private key generator found in the certificate manager supports SHA256WITHRSA now. This allows to sign your certificates using SHA-2 as some providers are moving away from SHA-1. Please remember that there might be OFTP2 programs out that cannot work with these certificates - please clarify this first before signing your certificates with SHA-2. *The send data transfer rate has been increased by better file access management *The local station showed up certificates and keys in the security tab - but there are just keys allowed to be selected *It is possible now to enable SSL client authentication per port - please remember that your partner could not connect if the remote system does not support this *It is possible to select the ciphers that are accepted by every SSL port. This allows to setup Perfect Forward Secrecy only. *TLS v1.1 and TLS v1.2 is supported now (OFTP2 Implementation Guideline v2.3) beneath TLS v1.0 *The data could be signed by SHA-256 and SHA-512 now. Odette has released a new implementation guideline in 01/2015 (OFTP2 Implementation Guideline v2.3). As there are some new qualifiers on the OFTP2 protocol level regarding the used cipher suites to sign data please ensure that your partner supports these cipher suites before you use them! Fixes: *If a certificate had been exported to p7b format it contained the end certificate only - without the trust chain certificates *There were problems if the certificate was not in PEM but additional BASE64 encoded if you tried to import it. This is very uncommon - we encountered this only once. *Importing certificates in p7b format now imports the full trust chain and the end certificate. In older versions just the end certificate was imported. *The certificates have not been sorted proper by their date in the display of the certificate manager. *A NullPointer occured if a file has been sent that didn't exist *There were wrong settings in the datasheet that has been created (under some rare circumstances) *Regression: The window size [OFTP2 protocol level] was always negotiated to 7, this slowed down the transmission speed *If an error occured during the generation of a Data Exchange Buffer the generation process hang and the transmission was not sent (happened very seldom) 3rd party software updates: *Update to BC 1.51 (crypto API, see https://www.bouncycastle.org/) *Update to Apache MINA 2.09 (client-server interface, see https://mina.apache.org/) Hint: The mendelson opensource OFTP2 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 "readme.txt" for further information about the product. --- Thank you all for your feedback and your help Your mendelson dev team Forum: OFTP2 [Less]

In reply to Fields requested by trading partner Thanks for the response. Actually I found a simple solution. Changing the Content-Type field from the default "EDI Consent" to "EDI-X12" turned out to be all that was needed. Log in or register to post comments

In reply to Upgrade Mendelson to b47 Thank you! I found and fixed this issue. This happened because there is a difference between jetty.xml configuration file in b39 and b47. In the guide it is said just to copy jetty.xml from the backup but it ... [More] doesn't work. The way to fix it is to copy only keystore file and edit access settings in jetty.xml existing in version b47 Log in or register to post comments [Less]

In reply to Upgrade Mendelson to b47 Roman, looks like missing jetty libs in the class path. Please ensure to add ... [More] jetty9/start.jar;jetty9/lib/annotations-api.jar;jetty9/lib/asm-5.0.3.jar;jetty9/lib/jetty-alpn-client-9.2.4.v20141103.jar;jetty9/lib/jetty-alpn-server-9.2.4.v20141103.jar;jetty9/lib/jetty-annotations-9.2.4.v20141103.jar;jetty9/lib/jetty-cdi-9.2.4.v20141103.jar;jetty9/lib/jetty-continuation-9.2.4.v20141103.jar;jetty9/lib/jetty-deploy-9.2.4.v20141103.jar;jetty9/lib/jetty-http-9.2.4.v20141103.jar;jetty9/lib/jetty-io-9.2.4.v20141103.jar;jetty9/lib/jetty-jaas-9.2.4.v20141103.jar;jetty9/lib/jetty-jndi-9.2.4.v20141103.jar;jetty9/lib/jetty-plus-9.2.4.v20141103.jar;jetty9/lib/jetty-proxy-9.2.4.v20141103.jar;jetty9/lib/jetty-rewrite-9.2.4.v20141103.jar;jetty9/lib/jetty-schemas-3.1.jar;jetty9/lib/jetty-security-9.2.4.v20141103.jar;jetty9/lib/jetty-server-9.2.4.v20141103.jar;jetty9/lib/jetty-servlet-9.2.4.v20141103.jar;jetty9/lib/jetty-servlets-9.2.4.v20141103.jar;jetty9/lib/jetty-util-9.2.4.v20141103.jar;jetty9/lib/jetty-webapp-9.2.4.v20141103.jar;jetty9/lib/jetty-xml-9.2.4.v20141103.jar;jetty9/lib/servlet-api-3.1.jar Regards Log in or register to post comments [Less]

Hi! The current version on the server is b39. (CentOS 6.5) I'm trying to upgrade to b47 and carefully following these instrusctions: Please copy the following files from your backup (step 1) to the installation: *certificates.p12 (your keystore for ... [More] encryption and signature) *jetty9/etc/keystore (your ssl keystore) *jetty9/etc/jetty.xml (your receipt web server settings) *notificationtemplates/* (your personal templates for the mail notification, skip this step if you haven't modified them) *.passwd (if you upgrade from b39 or younger) However, I always get the same error message when connect to GUI: /org/eclipse/jetty/xml/XmlConfiguration I'd appreciate if anyone can explain what I'm doing wrong I also attach the screenshot with the problem Thank you in advance! Forum: AS2 AttachmentSize Снимок экрана от 2015-01-12 14:03:40.png19.9 KB [Less]

In reply to Contact U via your SITE Shlomi, we received mails the last days, no idea what happened there. You could also send mails directly to service at mendelson dot de. Regards Log in or register to post comments

Hi, See attached picture Forum: Global AttachmentSize Unable to send e-mail26 KB

In reply to Ariba bdijk, hard to say, I would think this is a data issue. https://github.com/bcgit/bc-java/blob/master/mail/src/main/java/org/boun... --> https://github.com/bcgit/bc-java/blob/master/mail/src/main/java/org/boun... --> ... [More] https://github.com/bcgit/bc-java/blob/master/mail/src/main/java/org/boun... In function outputBodyPart of SMIMEUtil this line seems to be interesting: out = new CRLFOutputStream(out); Do you find CRLFs in your base64 part? Please have a look at http://www.ietf.org/rfc/rfc3851.txt for further investigation. Regards Log in or register to post comments [Less]

In reply to Ariba With the above change, we can communicate with Ariba, but I'm not able to understand what could be the root cause. How will calling SMIMESigned(signedMultiPart, base64) cause it to fail and SMIMESigned(signedMultiPart, binary) ... [More] cause it to work, whilst it looks like the signature is base64 encoded. Is this an issue in the BC libs? Log in or register to post comments [Less]

In reply to Fields requested by trading partner Neil, We designed the AS2 adapter just for the data transmission. That is the reason why we added no data content related preprocessing/data conversion capabilities/char replacement/postprocessing etc. ... [More] We offer a second system - the mendelson business integration - to populate data structures, convert them and monitor/schedule the communication interfaces like mendelson AS2. But this does not exist as community edition. Regards Log in or register to post comments [Less]