CData BizTalk Adapter for QuickBooks Online 2019 - Online Help
Questions / Feedback?

Migrating from 1.0 to 2.0 Tokens

CData BizTalk Adapter for QuickBooks Online 2019 - Build 19.0.7354

Intuit is removing support for OAuth 1.0 and switching to require everyone use OAuth 2.0 by the end of 2019. If you are currently using an older app and are concerned about a smooth transition for clients to migrate from 1.0 to 2.0, please use the following guide.

Obtain 2.0 Connection Credentials

Log into developer.intuit.com and navigate to My Apps. Open the app you are currently distributing to clients. 2.0 tokens will be generated along with 1.0 tokens. Obtain these values:

  • On OAuth 2.0 Keys, get the Client ID and Client Secret under Development. These are the OAuthClientId and OAuthClientSecret when UseSandbox is set to true.
  • On OAuth 2.0 Keys, get the Client ID and Client Secret under Production. These are the OAuthClientId and OAuthClientSecret when UseSandbox is set to false.
  • Modify the Redirect URI under both Development and Production. Set this to a valid URI you would like the app to redirect to. You will need to set this as your CallbackURL.
  • On Settings, write down the checked values under APIs. This will determine the 2.0 Scope you need to submit. You should have QuickBooks Accounting at the miinum already checked.

Automatically Perform Migration

If you have been using InitiateOAuth set to a minimum of REFRESH, then stored access tokens may be automatically migrated to 2.0 from 1.0. To do so, set the following connection properties:
  • OAuthClientId - Set this to the 2.0 Client ID for the same app.
  • OAuthClientSecret - Set this to the 2.0 Client Secret for the same app.
  • V1OAuthClientId - Set this to the 1.0 Client ID for the same app.
  • V1OAuthClientSecret - Set this to the 1.0 Client Secret for the same app.
  • CallbackUrl - Set this to the same value as marked in the Redirect URI in your app (2.0 keys section).
  • Scope - Set to "com.intuit.quickbooks.accounting" for QuickBooks Accounting, or "com.intuit.quickbooks.accounting com.intuit.quickbooks.payment" for both Accounting and Payments. Leaving it empty will result in "com.intuit.quickbooks.accounting" being used.

Once these connection properties are set, that's all you need. The next time the CData BizTalk Adapter for QuickBooks Online 2019 attempts to refresh the token, it will instead migrate the token to a 2.0 token. Internally the CData BizTalk Adapter for QuickBooks Online 2019 will automatically based on the stored token for othre requests.

Run the Migration Stored Procedure

If you are not using InitiateOAuth set to a minimum of REFRESH, you may manually refresh the token by calling the Migrate stored procedure. Before running the migration stored procedure, update your connection string and set the OAuth 2.0 Client ID and Secret. Then execute the MigrateToken stored procedure. Pass in these parameters:

  • Scope - Set to "com.intuit.quickbooks.accounting" for QuickBooks Accounting, or "com.intuit.quickbooks.accounting com.intuit.quickbooks.payment" for both Accounting and Payments.
  • CallbackUrl - Set this to the same value as marked in the Redirect URI in your app.
  • V1OAuthClientId - Set this to the 1.0 Client ID for the same app.
  • V1OAuthClientSecret - Set this to the 1.0 Client Secret for the same app.
  • V1OAuthAccessToken - Set this to the 1.0 OAuthAccessToken to be migrated. If not specified, it will be taken from the connection properties.
  • V1OAuthAccessTokenSecret - Set this to the 1.0 OAuthAccessTokenSecret to be migrated. If not specified, it will be taken from the connection properties.

After executing the Migration stored procedure, it will return with the 2.0 OAuthAccessToken and OAuthRefreshToken.

 
 
Copyright (c) 2020 CData Software, Inc. - All rights reserved.
Build 19.0.7354.0