MetaDefender Core Integration
How To Configure
Go to Settings → Core Integration. Choose Add MetaDefender Core.
In order to configure MetaDefender Core, fill out the necessary information on the configuration page:
- REST URL: used to enable communication between MetaDefender Managed File Transfer and MetaDefender Core and it should point to the machine where Metadefender Core is installed (i.e http://10.1.2.3:8008/metascan_rest)
- API Key: optional field that can be used in order to fine-tune the integration and restrict access for the MetaDefender Core installation.
- Default Workflow: Select the available workflow (as configured in MetaDefender Core) from the dropdown list to use
- User Agent: specify a user agent to filter rules (as configured in MetaDefender Core)
- Processing Timeout setting can be used to specify a timeout when waiting for results from MetaDefender Core. The timeout can be specify between 3 and 1000000 minutes.
Select actions to be taken when a file is blocked or when processing with MetaDefender Core fails: If you enable Delete the file, the file will be deleted once it is blocked.
When you are done, click on Update. MetaDefender Managed File Transfer will now process files with MetaDefender Core.
The list of available workflows is depending on the User Agent and API Key. If you change any of these two variable, a new list of items will be fetched. For further information: MetaDefender Core API documentation
Load balancing and high availability
Using the built-in round-robin algorithm
MetaDefender Managed File Transfer supports multiple MetaDefender Core servers for scenarios where load balancing / high availability is necessary. In order to add another server please repeat the steps above.
Using an external Layer 7 Load Balancer
Load balancing can also be achieved using an external Layer 7 load balancer in order to load-balance multiple MetaDefender Core servers. Using this architecture you can just configure MetaDefender Managed File Transfer to communicate with the load balancer directly. The load balancer needs to support sticky sessions (using cookies) in order for this scenario to work.
Please visit Using external Load Balancer page from MetaDefender Core user guide in order to learn more about this.