| Products | Versions |
|---|---|
| TIBCO BusinessConnect ebXML Protocol | 6.4.0 |
TIBCO BusinessConnect™ ebXML Protocol 6.4.0 hotfix 1 is now available. Customers entitled to Support will be able to download the Hotfix from the TIBCO Support Customer Portal Web UI using their username and password for the TIBCO Support Web page. Once logged on they can find the Hotfix under the Download Menu
AvailableDownloads/BusinessConnect/ebXML/6.4.0/hotfix-01
Listed below is a summary of updates included. Refer to the associated readme document for any additional information.
================================================================================
Closed Issues in 6.4.0_HF-001 (This Release)
EBMS-1885. ENTSOG compliance for ebms3/AS4.
Added suport for signing and encryption based on Elliptic Curve Keys.
For signing, we support the recommended EdDSA-25519 algorithm and also the alternative
option of ECDSA. For ECDSA the NIST curves P-256, P-384 and P-512 are supported.
Note : As per the ENTSOG spec, the recommended hash function for message digests is
SHA-256. So SHA-256 should be chosen for the message digest algorithm in the business
agreement doc exchange tab for spec compliance.
˜
For encryption, we support the recommended x-25519 key exchange along with HKDF key
derivation and AES-128-KW key encryption. We also support the alternative option of ECDH-ES
for key exchange. For ECDH-ES the NIST curves P-256, P-384 and P-512 are supported.
Note : As per the ENTSOG spec, AES-128-GCM is the recommended algorithm for the symmetric
encryption. So AES-128-GCM should be chosen for the encryption algorithm in the business
agreement doc exchange tab for spec compliance.
Note:Following the upgrade of the WSS4J libraries, encrypted SOAP transactions are currently failing for SOAP protocol.
EBMS-1939
ebxml retry fails again with status code HTTP 500 and 503
This fix includes retry mechanism for Synchronous reply mode when responder is downn,this will pick
the retry interval and retry time of protocol level settings.For this user has to set the property
ebxml.sync.retry.protocollevel (Boolean property set to true).
TIBCO BusinessConnect™ ebXML Protocol 6.4.0 hotfix 1 is now available