macOS DSN Configuration
This section shows how to set up ODBC connectivity and configure DSNs on macOS.
Minimum macOS Version
The CData ODBC Driver for AlloyDB driver requires macOS Sierra (10.12) or above.
Licensing the Driver
In a terminal, run the following commands to license the driver. To activate a trial, omit the <key> input.
cd "/Applications/CData ODBC Driver for AlloyDB/bin"
sudo ./install-license.sh <key>
You'll be prompted for a name and password. These refer to your name and your machine's password.
Connecting to AlloyDB
The following connection properties are required in order to connect to AlloyDB.
- Server: The host name or IP of the server hosting the AlloyDB database.
- Port (optional): The port of the server hosting the AlloyDB database. This property is set to 5432 by default.
- User: The user which will be used to authenticate with the AlloyDB server.
- Password: The password which will be used to authenticate with the AlloyDB server.
- Database (optional): The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
Authenticating to AlloyDB
Standard AuthenticationStandard authentication (using the user/password combination supplied earlier) is the default form of authentication.
No further action is required to leverage Standard Authentication to connect.
pg_hba.conf Auth Schemes
There are additional methods of authentication supported by the driver which must be enabled in the pg_hba.conf file on the AlloyDB server.
You may find instructions about authentication setup on the AlloyDB Server here.
You can authenticate using MD5 password verification by setting the auth-method in the pg_hba.conf file to md5.
The driver can authenticate by verifying the password with SASL (particularly, SCRAM-SHA-256).
To use this authentication method, set the auth-method in the pg_hba.conf file to scram-sha-256.
The authentication with Kerberos is initiated by AlloyDB Server when the CData ODBC Driver for AlloyDB is trying to connect to it. Set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB server, see Using Kerberos for details regarding how to authenticate with Kerberos by the driver.
Uninstalling the Driver
The easiest way to uninstall the driver is to open a terminal and run the included uninstall.sh script, located in the installation directory. For example:
cd "/Applications/CData ODBC Driver for AlloyDB"
Note: The script needs to be run from the installation directory.