Search

GlobalSCAPE Knowledge Base

Workflows fail that are configured to connect to servers that require SHA2

Karla Marsh
EFT

Viewable by Globalscape internal users only
If you want to provide this information to external users,
you must deliver it via other means, such as email.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • EFT v7 and later

SYMPTOM

AWE Workflows fail that are configured to connect to servers that require SHA2.

WORKAROUND

Move the SSH connection out of the AWE workflow and into EFT’s SSH engine, which supports SHA2. If you have multiple or complex Workflows, it may take a lot of time and effort to change the Workflows and Event Rules. If that is the case, you can engage Professional Services hours to do the work for you.

MORE INFORMATION

The Advanced Workflow Engine (AWE) uses a product from Network Automation called Automate, version 8, which uses an outdated SSH library that supports SHA1 but not SHA2. Workflows that need to connect to servers that require SHA2 will not be able to connect. Globalscape Engineering and Product Management are aware of it and are working to have our AWE module updated to Automate version 10, which does support SHA2. Upgrading EFT and AWE from Automate version 8 to version 10 will take quite some time to merge and thoroughly test. In the meantime, use the workaround below.

Details
Last Modified: 7 Years Ago
Last Modified By: kmarsh
Type: HOWTO
Article not rated yet.
Article has been viewed 1.8K times.
Options
Also In This Category