This section describes how to set up ODBC connectivity and configure DSNs on several Linux distributions: Debian-based systems, like Ubuntu, and Red Hat Linux platforms, like Red Hat Enterprise Linux (RHEL) and Fedora.

Minimum Linux Versions

Here are the minimum supported versions for Red Hat-based and Debian-based systems:

OS	Min. Version
Ubuntu	18.04
Debian	10
RHEL	8
Fedora	28
SUSE	15

Installing the Driver Dependencies

Run the following commands as root or with sudo to install the necessary dependencies:

• Debian/Ubuntu:
  

  apt-get install libc6 libstdc++6 zlib1g libgcc1

• RHEL/Fedora:
  

  yum install glibc libstdc++ zlib libgcc

Installing the Driver

You can use standard package management systems to install the driver.

On Debian-based systems, like Ubuntu, run the following command with root or sudo:

dpkg -i /path/to/driver/setup/SageIntacctODBCDriverforUnix.deb 

On systems that support the RPM package format, run the following command with root or sudo:

rpm -ivh /path/to/driver/SageIntacctODBCDriverforUnix.rpm 

Licensing the Driver

Run the following commands to license the driver. To activate a trial, omit the <key> input.

cd /opt/cdata/cdata-odbc-driver-for-sageintacct/bin/
sudo ./install-license.sh <key>

Connecting through the Driver Manager

The driver manager loads the driver and passes function calls from the application to the driver. You need to register the driver with the driver manager and you define DSNs in the driver manager's configuration files.

The driver installation registers the driver with the unixODBC driver manager and creates a system DSN. The unixODBC driver manager can be used from Python and from many other applications. Your application may embed another driver manager.

Creating the DSN

See Using unixODBC to install unixODBC and configure DSNs. See Using the DataDirect Driver Manager to create a DSN to connect to OBIEE, Informatica, and SAS.

Connecting to Sage Intacct

You can establish a connection to Sage Intacct using the embedded credentials (BasicReadOnly authentication), your own credentials (Basic authentication), or Okta credentials.

Authenticating to Sage Intacct

Sage Intacct supports three types of authentication: BasicReadOnly, Basic, and Okta.

You are ready to authenticate after you set these parameters:

• CompanyID: The ID you use to identify your company when logging into Sage Intacct.
• User: The login you use to log into Sage Intacct.
• Password The password for your login credentials.
• Basic authentication only:
  • SenderID: your SenderID.
  • SenderPassword: your SenderID's password.

BasicReadOnly

The driver has embedded Web Services credentials that are used when reading data from Sage Intacct. These credentials are read-only.

To authenticate, do the following:

1. Set AuthScheme to BasicReadOnly.
2. Ensure that you have not specified a SenderID or SenderPassword.
3. In your Web Services dashboard, navigate to the Company > Company Info > Security tab.
4. Navigate to Configuration > Company > Security > Web Services Authorizations / Edit.
5. Add "CData" to your Web Services authorizations. (Note: This is case-sensitive.)

Basic

You can use your own Web Services credentials to write data to Intacct.

To authenticate, set the following:

• AuthScheme: Basic.
• SenderID: The Web Services Sender ID assigned to you by Sage Intacct.
• SenderPassword: Your registered Web Services password.

Okta

To authenticate to Okta, set these properties:

• AuthScheme: Okta.
• User: The Okta user.
• Password: The Okta user's password.
• SSOLoginURL: The SSO provider's login URL.

Also set these SSOProperties:

• IntacctUserID: The Sage Intacct user ID that is mapped to the Okta user you set in the User connection property.
• APIToken (optional): If users are authenticated via a trusted application or proxy that overrides Okta client request context, specify the API Token that the customer created from the Okta organization.

Example connection string:

AuthScheme=Okta; SSOLoginURL='https://example.okta.com/home/appType/0bg4ivz6cJRZgCz5d6/46'; User=oktaUserName; Password=oktaPassword; SSOProperties='IntacctUserID=intacct_user';

Set the Driver Encoding

The ODBC drivers need to specify which encoding to use with the ODBC Driver Manager. By default, the CData ODBC Drivers for Unix are configured to use UTF-16 which is compatible with unixODBC, but other Driver Managers may require alternative encoding.

Alternatively, if you are using the ODBC driver from an application that uses the ANSI ODBC API it may be necessary to set the ANSI code page. For example, to import Japanese characters in an ANSI application, you can specify the code page in the config file '/opt/cdata/cdata-odbc-driver-for-sageintacct/lib/cdata.odbc.sageintacct.ini':

[Driver]
AnsiCodePage = 932