Controllers/AuthController.cs

@@ -7,68 +7,72 @@ using System.Threading.Tasks;
 
 namespace qbridge.Controllers
 {
-    [Route("api/[controller]")]
+    [Route("[controller]")]
     [ApiController]
     [Produces("application/json")]
-    public class AuthController : ControllerBase
+    public class OAuthRedirectController : ControllerBase
     {
 
-        public AuthController()
+
+        /*
+
+        Development tokens for QBOI oAuth2 "AyaNova_QBOI_2"
+
+        https://developer.intuit.com/v2/ui#/app/appdetail/b7urd26wgx/b7urd26xgp/keys
+
+        ClientID
+        ABj70Wv5gDauFd9KgKFwuvpQjfzTwEgodEG8tnBbS8mSQhNrZJ
+
+        Client Secret
+        XUmJyvEcEuwQuyhARUAm0a8G3gzbEAeMiATCLyFZ
+
+
+        Sandbox:
+        https://c50.sandbox.qbo.intuit.com/app/homepage
+        sandbox company_us_1
+        sandbox-quickbooks.api.intuit.com
+         */
+        public OAuthRedirectController()
         {
 
         }
 
-        // GET: api/Todo/5
-        [HttpGet("{login}/{password}")]
-        public async Task<ActionResult<QItem>> Get(string login, string password)
+        // Redirect endpoint
+        //Step 4 here: https://developer.intuit.com/app/developer/qbo/docs/develop/authentication-and-authorization/openid-connect
+        [HttpGet]
+        public IActionResult Get([FromQuery]string state, [FromQuery]string code)
         {
-            var QItem = new QItem();
-            QItem.Token1 = "Test token 1";
-            QItem.Token2 = System.DateTime.Now.ToString();
-            QItem.Token3 = login;
-
-            if (QItem == null)
-            {
-                return NotFound();
-            }
-
-            return QItem;
+            return Content($"State: {state}, Code: {code}");
         }
 
 
-        public class QItem
-        {
-
-            public string Token1 { get; set; }
-            public string Token2 { get; set; }
-            public string Token3 { get; set; }
-
-        }
 
 
-/*
-Plan: 
-Make a web APP and api that runs on our server and handles getting tokens from the QB Online oAuth2 endpoints
+        /*
+        Plan: 
+        Make a web APP and api that runs on our server and handles getting tokens from the QB Online oAuth2 endpoints
+        
+        Docs for normal development are here: https://developer.intuit.com/app/developer/qbo/docs/develop/authentication-and-authorization
 
-Tentative process:
+        Tentative process:
 
-Borrowing from the technique and concepts outlined here: http://relasoft.net/KB10004.html
-and here: https://github.com/IntuitDeveloper/C2QB-library-for-Windows-CUI-and-GUI/issues/1#issuecomment-511172847
+        Borrowing from the technique and concepts outlined here: http://relasoft.net/KB10004.html
+        and here: https://github.com/IntuitDeveloper/C2QB-library-for-Windows-CUI-and-GUI/issues/1#issuecomment-511172847
 
 
-User runs QBOI plugin, if it needs a new access token then it shells out to browser (with random temp session ID number to uniquely identify this user) to go to *our* qBridge auth page. 
-User enters their creds to login to QBOnline instance.
-QBridge passes creds (along with random session id as the extra parameter they allow) on to the QBOI auth page which when successful redirects browser to the QBridge page we've specified as the 
-"redirect url" with the tokens in the url and also our unique session ID which then shows the end user that it's success and stores the tokens somewhere (gonna need a db I guess) for fetching by QBOI.
+        User runs QBOI plugin, if it needs a new access token then it shells out to browser (with random temp session ID number to uniquely identify this user) to go to *our* qBridge auth page. 
+        User enters their creds to login to QBOnline instance.
+        QBridge passes creds (along with random session id as the extra parameter they allow) on to the QBOI auth page which when successful redirects browser to the QBridge page we've specified as the 
+        "redirect url" with the tokens in the url and also our unique session ID which then shows the end user that it's success and stores the tokens somewhere (gonna need a db I guess) for fetching by QBOI.
 
-Meanwhile, in the background, QBOI is polling a route on qbridge with the unique ID number looking for a return of the tokens it needs to proceed.  
-Once it fetches the "Access token" and "Refresh token" it needs successfully then it continues on to normal usage
+        Meanwhile, in the background, QBOI is polling a route on qbridge with the unique ID number looking for a return of the tokens it needs to proceed.  
+        Once it fetches the "Access token" and "Refresh token" it needs successfully then it continues on to normal usage
 
-If it gets a response that the token needs to be refreshed, it either hands this operation off to qBridge or does it itself (not sure at this point which way it's supposed to happen)
-If the access token expires after 100 days or so then they repeat this process (automatically by QBOI)
+        If it gets a response that the token needs to be refreshed, it either hands this operation off to qBridge or does it itself (not sure at this point which way it's supposed to happen)
+        If the access token expires after 100 days or so then they repeat this process (automatically by QBOI)
 
 
-*/
+        */
         // POST: api/Todo
         [HttpPost]
         public async Task<ActionResult<QItem>> Post(QCreds creds)
@@ -89,7 +93,7 @@ If the access token expires after 100 days or so then they repeat this process (
         }
 
 
-// *************************************************************************************************************
+        // *************************************************************************************************************