SSH failure when BusinessConnect tries to connect with a trading partner.
Article ID: KB0084628
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | - |
| Not Applicable | - |
Description
Description:
When BC tries to connect to a trading partner's SSH server, the connection fails. The following exception is observed in the Interior logs:
FTPGet Ssh Failure Reply #1: 500: SSH Exception: SshMgr: Ssh Transport creation failed: MyCompany ==> xx.yy.zz.aa:22: Key exchange failed: No match in kex params 'enc-algorithms-cli2srv', our's: aes128-cbc, peer's: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com (uc) [0]
Resolution
This issue is caused by BC not supporting the cipher that the trading partner server prefers. To work around the issue, go to the trading partner's protocol SSH transport screen (outbound) or BusinessAgreement transport SSH screen, and set the "Preferred Cipher" to "Any".
Issue/Introduction
SSH failure when BusinessConnect tries to connect with a trading partner.
Additional Information
BusinessConnect Trading Partner Administration Guide
Feedback
Yes
No
Powered by
