Why is the Skip Core Scanning feature not working in my MFT to MFT setup?

Introduction:

This knowledge base article provides a solution to the MFT to MFT synchronization when the Skip Core Scanning feature is enabled but since the upgrade to MFT version 3.9.1 or newer, this feature is not working anymore.

Details:

In the MFT version 3.7.4, a new feature was added to Skip Core Scanning. With this feature, during an MFT-to-MFT setup, on the source MFT, you can choose whether to skip Core scanning on the destination MFT.

To enhance security, we will introduce an additional setting. On the destination MFT, where the system-level API key is generated, these two settings must be enabled during API key generation: System level API Key and Allow Skip MetaDefender Core Scanning. If these settings are not enabled, the destination MFT will reject incoming extra headers. Even if the destination MFT supports them, it will still refuse these settings unless explicitly allowed.

What this means for you and how to proceed:

Starting from version 3.9.1, you will need to replace the existing API key used for the MFT to MFT integration on the receiving MFT with a new API key that has the new feature Allow Skip Core Scanning, as this is not an editable feature yet.

Please make sure to use the new API key with the Allow Skip Core Scanning option enabled on the source MFT.

Starting from version 3.9.2, you need to navigate to Global Settings → Integrations → API Keys, select the API key used for the Skip Core Scanning feature, edit it, and enable the Allow Skip Core Scanning option.