Connecting to Sage Intacct

To connect to Web Services, you will first need to enable the Web Services subscription. Navigate to Company > Admin Tab > Subscriptions and enable Web Services.

Intacct also recommends creating a Web Services-only user, which can be done by navigating to Company > Admin Tab and clicking on the + sign beside Web Services users.

You can establish a connection to Sage Intacct using either the embedded credentials or with your own credentials.

Authenticating to Sage Intacct

To authenticate, set CompanyID and set User and Password to the credentials you use to log on to Sage Intacct. In addition, you will need to either set your own SenderID and SenderPassword, or use the embedded credentials in the CData ADO.NET Provider for Sage Intacct.

BasicReadOnly

The provider has embedded Web Services credentials that are used when reading data from Intacct.

Follow these steps to authenticate:

• AuthScheme: Set this to BasicReadOnly.
• Ensure that you have not specified a SenderID or SenderPassword.
• In your Web Services dashboard, navigate to the Company > Company Info > Security tab.
• Add "CData" to your Web Services authorizations. This is case-sensitive. To do this, navigate to Company > Company Info (Configuration > Company in new UI) > Security > Web Services Authorizations / Edit.

NOTE: The embedded credentials are read-only. Use Basic for read and write access.

Basic

You can use your own Web Services credentials to write data to Intacct. Set the following to authenticate:

• AuthScheme: Set this to Basic.
• SenderID: Set this to the Web Services Sender ID assigned to you by Sage Intacct.
• SenderPassword: Set this to your registered Web Services password.

Okta

The following connection properties are used to connect to Okta:

• AuthScheme: Set this to Okta.
• User: Set this to the Okta user.
• Password: Set this to Okta password for the user.
• SSOLoginURL: Set this to the login url used by the SSO provider.

In addition, set the following SSOProperties:

• IntacctUserID: Set this value to the Intacct User ID that is mapped to the Okta user you set in the User connection property.
• APIToken (optional): Set this to the API Token that the customer created from the Okta organization. It should be used when authenticating a user via a trusted application or proxy that overrides Okta client request context.

The following is an example connection string:

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