MariaDB connections
DataMasque masks MariaDB tables in place. MariaDB and MySQL share most connection behaviour.
- Required privileges
- Connection parameters
- Encrypted connections
- Supported data types
- Unsupported key columns
Required privileges
A DataMasque connection for MariaDB requires:
CREATE TEMPORARY TABLESprivileges to the database.CREATE,DROP,INDEX,SELECT,UPDATE,INSERT,ALTERandREFERENCESprivileges to the target tables.
GRANT CREATE TEMPORARY TABLES ON <target database>.* TO <connection user>@<DataMasque host>;
GRANT CREATE, SELECT, UPDATE, INSERT, ALTER, REFERENCES ON <target database>.<target tables> TO <connection user>@<DataMasque host>;
Connection parameters
For MariaDB databases, the following fields are optional:
| MariaDB SSL Certificate | Choose an SSL Certificate to verify the server's certificate. These can be uploaded using the Files interface. |
| TLS | How DataMasque uses TLS: Prefer (default), Require or Off. See Encrypted connections. |
Encrypted connections
MariaDB uses the same encrypted connection settings as MySQL,
including the TLS choice (Prefer (default), Require or Off),
the verification of the server certificate when an SSL certificate is selected,
and the TLS fallback warning under Prefer.
See MySQL connections -> Encrypted connections.
Amazon RDS for MariaDB 11.8 and later rejects unencrypted connections by default
(require_secure_transport is on).
DataMasque connects to these databases without extra configuration.
Supported data types
MariaDB supports the same data types as MySQL. See MySQL connections -> Supported data types.
Unsupported key columns
MariaDB has the same unsupported key column types as MySQL. See MySQL connections -> Unsupported key columns.