With the release of version 220.127.116.11 of the Masking Engine, the Mapping Algorithm now provides support for storing all mappings on a user-supplied database. This enables users to share mappings for the same Mapping Algorithm across engines. The mapping database connection info can be provided when a Mapping Algorithm is added or edited.
In order to serve as a mapping database, the following requirements must be met:
- The database must be a PostgreSQL database version 9.5 or newer.
- The database must be reachable by the Masking Engine
All necessary tables and functions to successfully run the Mapping Algorithm will be created by the Masking Engine upon connection to the remote mapping database.
Remote mappings are managed in the same way as local mappings via the Masking Engine GUI or APIs.
It is completely fine to use the same remote database for multiple Mapping Algorithms on the same Masking Engine or across many Masking Engines.
Given that the Masking Engine will need to query the remote database, network latency will have an effect on how fast a job running a Mapping Algorithm will run, especially on the "initial" run of a Mapping Algorithm when the majority of new mappings are established.
By opting to manage their own mappings, the user agrees to be responsible for:
- Database uptime
- Database security
- Network connectivity
- Database storage
Configuring the connection¶
The user may opt to configure their PostgreSQL database however they wish. With the exception of host, port, database and schema, all other connection properties may be provided via a properties file, per the PostgreSQL JDBC Driver documentation.
For databases with SSL/TLS connections, the correct properties shoudl be supplied via the properties file.