Determine the URLs for the Authorization Server for the service you are using. With OAuth 2.0, the following URLs will need to be specified:
The Request Token Endpoint URL: this is used in the first request to initiate the OAuth process, and needs to be specified in the InitializeOAuth step.
The Access Token Endpoint URL: this is the URL that is used in the final step to retrieve an Access Token that can be used to access the protected resource. This URL needs to be specified in the FinalizeOAuth step.
Run the InitializeOAuth Choreo, specifying the Client ID for the app you registered with a particular service. The InitializeOAuth Choreo will return an authorization URL and a callback ID (required for the FinalizeOAuth step).
Open a new tab and navigate to the authorization URL returned by the InitializeOAuth Choreo. Click "allow" to grant the app access to your account.
Run the FinalizeOAuth Choreo, specifying the callback ID returned earlier by the InitializeOAuth choreo, to obtain an OAuth access token that can be used to access the API.
Important: These Choreos are designed to support standard OAuth 2.0 implementations. OAuth 2.0 frameworks that do not support the reserved OAuth state parameter discussed in sections 4.1.1 and 4.1.2 of the OAuth 2.0 spec are not supported at this time. These Choreos have been tested with all APIs using OAuth 2.0 in the Temboo Library. Note that the Dwolla API does not support using the OAuth state parameter in Redirect URIs, so if you need an OAuth Library for Dwolla, you should use the OAuth helpers associated specifically with the Dwolla bundle found here.