Library . RunKeeper . OAuth . InitializeOAuth

Generates an authorization URL that an application can use to complete the first step in the OAuth process.

Input
• ClientID The Client ID provided by RunKeeper after registering your application.
Optional Input
• CustomCallbackID A unique identifier that you can pass to eliminate the need to wait for a Temboo generated CallbackID. Callback identifiers may only contain numbers, letters, periods, and hyphens.
• ForwardingURL The URL that Temboo will redirect your users to after they grant access to your application. This should include the "https://" or "http://" prefix and be a fully qualified URL.
Log In To Run
• Output
  Actuator Trigger Condition

  If{"AuthorizationURL":{"type":"string","description":"The authorization URL that the application's user needs to go to in order to grant access to your application."},"CallbackID":{"type":"string","description":"An ID used to retrieve the callback data that Temboo stores once your application's user authorizes."},"Success":{"type":"boolean"}}Authorizatio...CallbackIDSuccess then write

  High Low

  to at

  • AuthorizationURL The authorization URL that the application's user needs to go to in order to grant access to your application.
  • CallbackID An ID used to retrieve the callback data that Temboo stores once your application's user authorizes.
• CHOREO CLASS

  • /*
    TembooTask class placeholder
    */

• iOS HEADER

  • /*
    TembooTask header placeholder
    */

• • Simple
  Enhanced
  Add a sensor via the virtual pin board above to generate code for sensor data graphs.
  Compiled
  Add a sensor or actuator via the virtual pin board above to generate compiled code for sensor data graphs and remote actuator control.
  Device Configure Changed

  Since you've changed your device configuration, you'll need to tell us about this new device.

  Update Device
  1. Add a sensor or actuator to your device.
  2. Register your board and download your code.

  Download
  • Download editable code
  • Commit to GitHub
  • Send to CCS Cloud

  OK! Let's set up your device

  This feature is in experimental mode - pricing coming soon.

  Device Name *

  Device ID

  Description

  Location *

  Use lat/long

  Sensor Data
  Frequency *

  Pro Tip!

  Power consumption will increase if you choose a higher frequency.

  Every 30 seconds Every minute Every 5 minutes Every 30 minutes Every hour Every day Custom interval

  Safeguard data

  what's this?

  If connectivity is lost, up to 2MB of data will be stored locally on your device, and updated when connectivity is restored.

  + new tag

  Save
  Commit your generated code
  and collaborate with others.

  Send your code straight to a GitHub repository.

  Collaborating on GitHub?

  Your code will be visible by others in your repos. Keep credentials private by saving a Profile or commit code with Placeholder inputs.

  Choose a GitHub Repository

  Name:

  The following files will be added to this repo:

  * Don't worry! Your credentials and any inputs that aren't saved in a Profile will not be included.

  Success!

  Visit the link below to view, modify, and share code.

  Cancel Commit code to GitHub Use Placeholders Save a Profile Commit Close
  Send code to CCS Cloud.

  You'll be able to edit and share your code from TI's CCS Cloud IDE.

  Name your application

  Names can only contain letters, numbers, hyphens, and underscores.

  The following will be sent to CCS Cloud:

  TembooMain.c

  TembooAccount.h

  instructions.txt

  + 9 others

  Success!

  Visit the link below to view, modify, and share code.

  https://dev.ti.com/ide/

  Cancel Send to CCS Cloud Send Close
  Code

  • // Instantiate the Choreo, using a previously instantiated TembooSession object, eg:
    // TembooSession session = new TembooSession("accountName", "myFirstApp", "abc123xxxxxxxxxxxxxx");
    
    InitializeOAuth initializeOAuthChoreo = new InitializeOAuth(session);
    
    // Get an InputSet object for the choreo
    InitializeOAuthInputSet initializeOAuthInputs = initializeOAuthChoreo.newInputSet();
    
    // Set inputs
    
    // Execute Choreo
    InitializeOAuthResultSet initializeOAuthResults = initializeOAuthChoreo.execute(initializeOAuthInputs);

• Header File

  • /* 
    A header file containing your Temboo account information will appear here once you've
    configured your device above.
    */

• Proxy Code

  • /*
    Please log in to generate proxy server code for use with the JavaScript SDK.
    */

• Notes

  • This Choreo generates an authorization URL that an application can use to complete the first step in the OAuth process. A unique and private callback URL for your account is registered with Temboo so that when you redirect your user to the AuthorizationURL returned by the Choreo, the authorization code generated by RunKeeper is stored temporarily for easy retrieval in the finalization step of the OAuth process. You can complete the OAuth process by passing the CallbackID (returned by this Choreo), to the FinalizeOAuth Choreo.

    In some cases, you may want to design your application such that you don't have to wait for this Choreo to return the CallbackID. If you find yourself in this situation, you can specify a CustomCallbackID, and then your code can move onto something else. Once you've detected that your user has clicked "allow", you can pass your CustomCallbackID to the FinalizeOAuth Choreo in order to complete the process. Just remember that a CustomCallbackID should be unique. Concatenating a serial timestamp and a randomized string would be a reasonable CustomCallbackID for example.

    Here's an example of acceptable inputs:

    ClientID = {YOUR RUNKEEPER CLIENT ID}
    ForwardingURL = http://example.com