Still using OAuth 1.0, even for your new users? If you haven’t built and tested your OAuth 2.0 functionality yet, you’ll likely find it’s much easier to implement the OAuth 2.0 than it was to implement OAuth 1.0.
According to our latest research, developers who’ve migrated spent 20 to 40 hours to fully implement, test, and deploy OAuth 2.0 for new connections (new users), after they created their plan. This is usually the bulk of the overall migration effort. The actual migration of existing users after that is pretty quick.
OAuth 2.0 implementation resources
Here’s a quick list of resources that can help you with your OAuth 2.0 implementation:
#1: Install your preferred OAuth 2 client library to get started. We support PHP, Node.js, .Net, Go, Java, Python, and Ruby. Note: If you use the ConsoliBYTE QuickBooks PHP DevKit, see their GitHub repo for instructions.
#2: Check out our docs and videos for tips on how to implement OAuth 2.0:
Video: OAuth 2.0 Token Life Cycle
#3: When you’re ready to start routing new users to your OAuth 2.0 sign-in flow in Production, and if your app is listed on Apps.com, update your App settings, as described in the OAuth Migration doc.
Reminder: This setting only applies to apps on Apps.com, and it only affects users who go through your Connect to QuickBooks flow to grant your app access to their QuickBooks company data. It won’t affect existing users who are still using OAuth 1.0 tokens.
#4: Track your progress! Sign in to your OAuth Migration Mission and check off “Implement OAuth 2.0” and “Start accepting OAuth 2.0 connections,” and then get ready your final step!
You’re soooo close now! You just need to migrate your existing users <link to next blog post for step 7> from OAuth 1.0 to OAuth 2.0. That step usually only takes an hour or two!
And, to help you celebrate when you’re done, we’ll give you 250 points on The Bridge after you fully complete your migration. As always, please feel free to ask questions about OAuth migration in our OAuth help community!