Security and Authentication

To protect data from unauthorized access, some MariaDB data stores require connections to be authenticated with user credentials or encrypted using the SSL protocol. The Simba MariaDB ODBC Connector provides full support for these authentication protocols.

Note: In this documentation, "SSL" refers to both TLS (Transport Layer Security) and SSL (Secure Sockets Layer). The connector supports . The SSL version used for the connection is the highest version that is supported by both the connector and the server.

Note: In this documentation, "SSL" refers to both TLS (Transport Layer Security) and SSL (Secure Sockets Layer). The SSL version used for the connection is the highest version that is supported by both the connector and the server. By default, the connector supports TLS 1.0, 1.1, and 1.2. You can configure the connector to use a specific TLS version. For more information, see Configuring SSL Connections in Windows or Configuring SSL Connections on a Non-Windows Machine.

The connector provides a mechanism that enables you to authenticate your connection using your MariaDB user name and password authentication. For detailed connector configuration instructions, see Creating a Data Source Name in Windows or Creating a Data Source Name on a Non-Windows Machine.

Additionally, the connector supports the following types of SSL connections:

• No identity verification
• One-way authentication
• Two-way authentication

It is recommended that you enable SSL whenever you connect to a server that is configured to support it. SSL encryption protects data and credentials when they are transferred over the network, and provides stronger security than authentication alone. For detailed configuration instructions, see Configuring SSL Connections in Windows or Configuring SSL Connections on a Non-Windows Machine.