OAuth2 Web Forms Sample app for Dotnet for Payments API The Intuit Developer team has written this OAuth 2.0 Sample App in .Net(C#) to provide working examples of OAuth 2.0 concepts, and how to integrate with Intuit endpoints and make Payments API calls.
Before beginning, it may be helpful to have a basic understanding of OAuth 2.0 concepts. There are plenty of tutorials and guides to get started with OAuth 2.0. Check out the docs on https://developer.intuit.com/
.Net Framework 4.6.1
Clone this repository/Download the sample app.
All configuration for this app is located in web.config. Locate and open this file.
We will need to update 5 items:
- clientId
- clientSecret
- redirectUri
- appEnvironment (sandbox/production)
- logPath
First 3 values must match exactly with what is listed in your app settings on developer.intuit.com. If you haven't already created an app, you may do so there. Please read on for important notes about client credentials, scopes, and redirect urls. logPath should be the location of a physical path on your disk.
Once you have created an app on Intuit's Developer Portal, you can find your credentials (Client ID and Client Secret) under the "Keys" tab. You will also find a section to enter your Redirect URI here.
You'll have to set a Redirect URI in both 'web.config' and the Developer Portal ("Keys" section). With this app, the typical value would be http://localhost:59785/Default.aspx, unless you host this sample app in a different way (if you were testing HTTPS, for example or changing the port).
After setting up both Developer Portal and your web.config(setup Log Path too), run the sample app. Check logs on the path you have already configured in the web.config to get details of how the flow worked.
All flows should work, please note the scope in each of these flows. The sample app supports the following flows:
This flow requests OpenID only scopes. After authorizing (or if the account you are using has already been authorized for this app), the redirect URL will parse the JWT ID token, and make an API call to the user information endpoint.
This flow requests OAuth scopes. You will be able to make a Payments API sample call (using the OAuth2 token) on the /connected landing page.
This flow requests both OpenID and OAuth 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.