This commit is contained in:
2019-09-27 15:14:19 +00:00
parent a30e3ecec7
commit f91c8e4796
2 changed files with 12 additions and 1 deletions

View File

@@ -54,7 +54,6 @@ namespace qbridge.Controllers
Client Secret
XUmJyvEcEuwQuyhARUAm0a8G3gzbEAeMiATCLyFZ
Sandbox:
https://c50.sandbox.qbo.intuit.com/app/homepage
sandbox company_us_1

12
notes.txt Normal file
View File

@@ -0,0 +1,12 @@
TODO:
Modify QBOI to use the new token system but just statically coded in and do a test build and see if can access and do ops via qboi with sample data
Use the QBridge code as is to fetch a token for testing, build qboi with the token embedded and see if it works.
If that works then plan and institute a publishable solution.
- We don't want to store their tokens if possible so try to do it without any token storage
- Maybe they generate a one time code that they send to the Start route which in turn they can fetch from memory off the server later via qboi
- QBOI only holds the token until they fetch it via qboi
- QBOI probably will be able to refresh the token any time as there is no redirect url required for refreshment
- So QBridge is only required for the initial authorization process after which QBOI can operate using the refresh token scheme until that expires at which point QBOI can simply redirect to the QBridge again