API Docs & Tools Blog Help
Changes to the Integrated Application Authentication for QuickBooks Desktop users - Intuit Developer Community Blog

June 17, 2016 | William Lorfing

Changes to the Integrated Application Authentication for QuickBooks Desktop users

Update, 7/7/2016:

  • Note that these changes will be put into effect for QuickBooks 2015(R10 – US, CA, and UK)
  • Clarified some of the details regarding the implementation and authorization required.

Update, 6/23/2016:  Note that these changes will be put into effect for QuickBooks 2016(R7 – US, CA, and UK)


Intuit is reinforcing existing security features that help protect QuickBooks customers’ sensitive information.

As a result of this effort, Intuit is delivering an update that impacts third-party applications that connect to QuickBooks Desktop using the QuickBooks XML SDK.

There is no impact to QB XML SDK applications that access QuickBooks Desktop while being used by a QuickBooks user. Rather, the update might affect applications where the desktop application runs in unattended mode (e.g., shopping cart integration via web connector).

The earlier concept of an LGB file that provided access to QB XML SDK apps has been deprecated. A new file specific to a Windows user in a given machine is created on user login that provides access to a QB XML SDK app in QuickBooks.

The implementation of this update will require customers to re-enter their login-in credentials.

  • Once the update is installed, each user on every computer used to access QuickBooks Desktop will be required to log in to QuickBooks to enable the QB XML SDK application to connect or the Admin can login to QuickBooks on each computer for the first time after the upgrade and this will automatically authorize all of the applications for all of the users previously authorized to access the apps. This will also remove the .LGB file which was present earlier.
  • Customers will also be asked to log in if access levels of a third-party application are changed, a new application is added to the list of QB XML SDK applications, or if the QuickBooks password has been changed. If there is a password change, , it should be the respective user who should login to the QuickBooks UI to complete the update. If a new app needs to be authorized, the Admin should log in to authorize the app for the first time.
  • Customers using QuickBooks Desktop on a single computer in a multi-user mode will need to ensure that the administrator/ or users on that computer have logged-in at least once.
  • User-specific apps will require the individual user to log in once the update has been installed. Also a new “Reauthorize” button has been added in the Integrated App Preferences that will generate the new config files for the QB XML SDK apps running in unattended mode. This button is only enabled for the Admin, while in single user mode, and this will generate the entries for all the apps authorized to run in unattended mode when selected.
  • If your application runs as a different windows user, make sure you log in to that windows session and open QuickBooks using the user that your application is running as.

If the company file has Personally Identifiable Information (PII) in QuickBooks, users will be required to login with a password; the SDK app will only be allowed to connect once the login has been completed for that user.

When logging in, customers will be instructed to set up a strong password. Customers should use unique letters and numbers in a password, not basic words that can easily be found online or in the dictionary.

Thank you for your patience and ongoing partnership as we implement these important security updates.


View all
Load more comments