From f91c8e47965d8522ba044b2f23d460cd4eb79c81 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 27 Sep 2019 15:14:19 +0000 Subject: [PATCH] --- Controllers/AuthController.cs | 1 - notes.txt | 12 ++++++++++++ 2 files changed, 12 insertions(+), 1 deletion(-) create mode 100644 notes.txt diff --git a/Controllers/AuthController.cs b/Controllers/AuthController.cs index f5778c1..502834b 100644 --- a/Controllers/AuthController.cs +++ b/Controllers/AuthController.cs @@ -54,7 +54,6 @@ namespace qbridge.Controllers Client Secret XUmJyvEcEuwQuyhARUAm0a8G3gzbEAeMiATCLyFZ - Sandbox: https://c50.sandbox.qbo.intuit.com/app/homepage sandbox company_us_1 diff --git a/notes.txt b/notes.txt new file mode 100644 index 0000000..cb7d074 --- /dev/null +++ b/notes.txt @@ -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 + +