Mapping templates are used for rapid configuration of complex back-end applications with maximal security. A template is a mapping that is pre-configured with all the rules, exceptions and security settings required to get the application up and running. Select a template name to create a mapping based on that template.
Templates for Microsoft Products
The mapping templates below are used for Microsoft products and allows to integrate them easily. Product- and version-specific integration manuals are found on Techzone.
Name | Description |
Exchange 2016 Outlook Web Access | Enable high-security protection of Outlook Web Access (OWA) through Airlock Gateway. |
Exchange 2016 Outlook Anywhere | Allow Outlook to securely access Exchange through the Internet, using RPC over HTTP(S). |
Exchange 2016 ActiveSync | Secure synchronization between Exchange and mobile clients. |
SharePoint 2016 | All recommended settings to protect a SharePoint server. |
Exchange 2019 OOTW | Enable high-security protection of Outlook on the Web (OOTW) through Airlock Gateway. |
Exchange 2019 Outlook Anywhere | Allow Outlook to securely access Exchange through the Internet, using RPC over HTTP(S). |
Exchange 2019 ActiveSync | Secure synchronization between Exchange and mobile clients. |
SharePoint 2019 | All recommended settings to protect a SharePoint server. |
WebDAV for IIS | All recommended settings to protect a WebDAV for IIS. |
The description below shows the necessary steps to make custom mapping templates available in Airlock Configuration Center.
- 1.Sign in to Configuration Center as an admin.
- 2.Go to Application Firewall - Reverse Proxy and select the mapping, which should become a custom mapping template on Airlock Gateway.
- 3.Disconnect the virtual hosts and back-end group from the mapping.
- 4.Click on the Export Mapping icon and save the file.
To deploy the previously exported mapping as a custom mapping template, copy it to the following folder on Airlock Gateway:
/opt/airlock/custom-settings/mgt-agent/templates/<folder name>/<mapping template>
- 1.<folder name>: This folder is used in the Configuration Center to group the mapping templates.
- 2.<mapping template>: This is the mapping template exported previously.
Naming convention:
The following naming convention is used for the folder name and the mapping template.
- 1.Dash: The first part of the name until the - will be cut away. If the name does not contain any "-", nothing will be cut away.
- 2.File extension: The file extension must be '.zip' and will be cut away.
- 3.Underscore: The _ will be replaced with a space.
The custom mapping template will be available in the Configuration Center instantly. There are no further actions required after copying the file to Airlock Gateway.
Example:
The example below shows how custom mapping templates can be deployed on Airlock Gateway.
/opt/airlock/custom-settings/mgt-agent/templates/10-Ergon/10-Airlock_IAM_Client_Certificate.zip
/opt/airlock/custom-settings/mgt-agent/templates/10-Ergon/15-Airlock_IAM_Frontside_Kerberos.zip
/opt/airlock/custom-settings/mgt-agent/templates/15-Opensource/10-Joomla.zip
/opt/airlock/custom-settings/mgt-agent/templates/15-Opensource/15-Typo3.zip
/opt/airlock/custom-settings/mgt-agent/templates/15-Opensource/20-PHP_MyAdmin.zip
- ●Make sure that exported mappings are only used on equal or newer Airlock versions. It is not possible to use an exported mapping on an older Airlock system!
- ●It is best practice to use numbers in "folder name" and "mapping template" (see example above). This way it is possible to place a group or custom mapping template on a specific place in the list.