Skip to content
OAuth2 sample app using Go
Go HTML CSS
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
cache
config
handlers
static
views
LICENSE.txt
README.md made the code more go getable May 22, 2018
config.json
main.go

README.md

Sample Banner

OAuth2 - Go Sample App

The Intuit Developer team has written this OAuth 2.0 Sample App in Go programming language to provide working examples of OAuth 2.0 concepts, and how to integrate with Intuit endpoints.

Table of Contents

Requirements

In order to successfully run this sample app you need a few things:

  1. Go installation
  2. A developer.intuit.com account
  3. An app on developer.intuit.com and the associated client id and client secret.

First Use Instructions

  1. go get -d github.com/IntuitDeveloper/OAuth2-Go
  2. Fill in the config.json file values (clientId, clientSecret) by copying over from the keys section for your app.

Running the code

Once the sample app code is on your computer, you can do the following steps to run the app:

  1. Install the sample using the following commands
    cd $GOPATH/src/github.com/IntuitDeveloper/OAuth2-Go
    go install
  2. Run the sample by using one of the two commands below
    $GOPATH/bin/OAuth2-Go
    or
    OAuth2-Go
  3. Wait until the terminal output displays the "running server on :9090" message.
  4. Your app should be up now in http://localhost:9090/
  5. The oauth2 callback endpoint in the sample app is http://localhost:9090/oauth2redirect
  6. To run the code on a different port, update the property "port" in config.json. Also make sure to update the redirectUri in config.json and in the Developer portal ("Keys" section).

Configuring the callback endpoint

You'll have to set a Redirect URI in the Developer Portal ("Keys" section). With this app, the typical value would be http://localhost:9090/oauth2redirect, unless you host this sample app in a different way (if you were testing HTTPS, for example).

Note: Using localhost and http will only work when developing, using the sandbox credentials. Once you use production credentials, you'll need to host your app over https.

Getting the OAuth Tokens

The sample app supports the following flows:

Sign In With Intuit - this flow requests OpenID only scopes. Feel free to change the scopes being requested in config.json. After authorizing (or if the account you are using has already been authorized for this app), the redirect URL (/oauth2redirect) will parse the JWT ID token, and make an API call to the user information endpoint.

Connect To QuickBooks - this flow requests non-OpenID scopes. You will be able to make a QuickBooks API sample call (using the OAuth2 token) on the /connected landing page. Sample implementation for RefreshToken and RevokeToken is also available in that page.

Get App Now (Connect Handler) - this flow requests both OpenID and non-OpenID scopes. It simulates the request that would come once a user clicks "Get App Now" on the apps.com website, after you publish your app.

Scope

It is important to ensure that the scopes your are requesting match the scopes allowed on the Developer Portal. For this sample app to work by default, your app on Developer Portal must support Accounting scopes. If you'd like to support both Accounting and Payment, simply add thecom.intuit.quickbooks.payment scope in the config.json file.

Storing the tokens

This app stores all the tokens and user information in a cache. For production ready app, tokens should be encrypted and stored in a database.

Discovery document

The app calls the discovery API during starup and loads all the endpoint urls. For production ready app, make sure to run this API once a day to get the latest urls.

You can’t perform that action at this time.