MariaDB Connection
The MariaDB connection type enables automations to execute queries, run stored procedures, and perform data operations against MariaDB database servers. It is used by the plugin-sql-databases plugin, which delegates to the sql-database-connector.
Connection Type
| Property | Value |
|---|---|
| Type ID | MARIADB |
| Category | Relational Databases |
| Testable | Yes |
| Entity class | DBConnectionDetails |
Friendly Example
| What you enter | Example |
|---|---|
| Connection name | MariaDB - Operations Data |
| Used for | Reading operational records for daily checks and automated reports |
| Main details to collect | Host, port, database name, username, and password |
| Best person to provide it | Database administrator |
After it is saved, workflow builders select MariaDB - Operations Data in a node instead of entering these details again.
Connection Modes
The MariaDB connection supports two modes. Choose the one that matches how your credentials are stored.
| Mode | When to use |
|---|---|
| All Details | Provide host, port, database name, username, and password individually. The platform builds the JDBC URL automatically. |
| JDBC URL | Paste a full JDBC connection string directly. Useful when your DBA provides a pre-built URL. |
Mandatory Fields
| Field | What It Means | Example |
|---|---|---|
host | Hostname or IP address of the MariaDB server | mariadb.internal.example.com |
port | TCP port MariaDB is listening on. Default is 3306. | 3306 |
database | Name of the database (schema) to connect to | operations_db |
username | Login name of the database user | qinfinite_automation |
password | Password for the database user. Encrypted at rest. | •••••••• |
When using JDBC URL mode, replace the individual host/port/database fields with a single jdbcUrl string in the format shown below.
JDBC URL Format
jdbc:mariadb://host:port/database
Example:
jdbc:mariadb://mariadb.internal.example.com:3306/operations_db
SSL/TLS in the JDBC URL
To require an encrypted connection, append SSL parameters:
jdbc:mariadb://mariadb.internal.example.com:3306/operations_db?useSSL=true&requireSSL=true&verifyServerCertificate=true
Advanced Fields
| Field | What It Means | Example |
|---|---|---|
sslMode | SSL enforcement level. Options: disabled, preferred, required, verify-ca, verify-full. Defaults to preferred. | required |
connectionTimeout | Maximum time in milliseconds to wait when establishing a connection before failing. | 10000 |
tcpKeepAlive | Send TCP keepalive packets to prevent idle connections from being dropped by firewalls or NAT gateways. Set to true to enable. | true |
Setup Instructions
-
Locate your MariaDB server. Confirm the hostname (or IP address) and the port MariaDB is listening on. The default port is
3306. If you are connecting through a reverse proxy or SSH tunnel, use those coordinates instead. -
Create a dedicated database user with the minimum permissions required by your workflows:
CREATE USER 'qinfinite_automation'@'%' IDENTIFIED BY 'strong-password';
GRANT SELECT, INSERT, UPDATE, DELETE ON operations_db.* TO 'qinfinite_automation'@'%';
FLUSH PRIVILEGES;Replace
operations_dbwith your target database name and restrict the host wildcard (%) to the platform's IP if your security policy requires it. -
Verify network access. The Qinfinite platform must be able to reach port
3306(or your custom port) on the MariaDB host. Update firewall rules or security groups if needed. -
Create the connection in the Global Configurator using the host, port, database name, and credentials from the steps above.
-
Test the connection. Click Test Connection to confirm the credentials and network path are correct before saving.
Troubleshooting
| Symptom | Likely Cause |
|---|---|
Connection refused or Communications link failure | The platform cannot reach the MariaDB host on the specified port. Check the host, port, firewall rules, and whether the MariaDB service is running. |
Access denied for user '...'@'...' | Wrong username, password, or the user is not permitted to connect from the platform's IP address. Verify the GRANT statement includes the correct host pattern. |
Unknown database 'xyz' | The database name does not exist on the server. Double-check the name against the actual schema list. |
SSL connection error | The server requires SSL but the JDBC URL does not include SSL parameters, or the certificate presented by the server is not trusted. Add useSSL=true and the appropriate verifyServerCertificate setting to the URL. |