Cmdlets for Basecamp

Build 20.0.7587

Headless Machines

Using OAuth on a Headless Machine

To create Basecamp data sources on headless servers or other machines on which the cmdlet cannot open a browser, you need to authenticate from another machine. Authentication is a two-step process.

  1. Instead of installing the cmdlet on another machine, you can follow the steps below to obtain the OAuthVerifier value. Or, you can install the cmdlet on another machine and transfer the OAuth authentication values, after you authenticate through the usual browser-based flow.
  2. You can then configure the cmdlet to automatically refresh the access token from the headless machine.
You can follow the headless OAuth authentication flow using the cmdlet's embedded OAuth credentials or using the OAuth credentials for your custom OAuth app.

Using the Embedded OAuth Credentials

Obtain a Verifier Code

Follow the steps below to authenticate from another machine and obtain the OAuthVerifier connection property:

  1. Click the following link to open the Basecamp OAuth endpoint in your browser.
  2. Log in and grant permissions to the cmdlet. You are then redirected to the callback URL, which contains the verifier code.
  3. Save the value of the verifier code. You will set this in the OAuthVerifier connection property.

On the headless machine, set the following connection properties to obtain the OAuth authentication values.

  • OAuthVerifier: Set this to the verifier code.
  • InitiateOAuth: Set this to REFRESH.
  • OAuthSettingsLocation: Set this to persist the encrypted OAuth authentication values to the specified file.
  • AccountId: Copy this from the URL after you log into Basecamp:
    https://basecamp.com/<AccountId>

After the OAuth settings file is generated, set the following properties to connect to data:

  • OAuthSettingsLocation: Set this to the file containing the encrypted OAuth authentication values. Make sure this file gives read and write permissions to the cmdlet to enable the automatic refreshing of the access token.
  • InitiateOAuth: Set this to REFRESH.
  • AccountId: Copy this from the URL after you log into Basecamp:
    https://basecamp.com/<AccountId>
  • Schema: Set this to "V2" or "V3" to connect to Basecamp 2 or Basecamp 3 accounts.
  • ProjectId: For most table operations, a ProjectId is a required parameter. You can query the Projects table to obtain this value.

Transfer OAuth Settings

Follow the steps below to install the cmdlet on another machine, authenticate, and then transfer the resulting OAuth values.

On a second machine, install the cmdlet and connect with the following properties set:

  • OAuthSettingsLocation: Set this to a writable text file.
  • AccountId: Copy this from the URL after you log into Basecamp:
    https://basecamp.com/<AccountId>
Test the connection to authenticate in the browser. The resulting authentication values are written, encrypted, to the path specified by OAuthSettingsLocation. Once you have successfully tested the connection, copy the OAuth settings file to your headless machine.

On the headless machine, set the following connection properties to connect to data:

  • InitiateOAuth: Set this to REFRESH.
  • OAuthSettingsLocation: Set this to the path to your OAuth settings file. Make sure this file gives read and write permissions to the cmdlet to enable the automatic refreshing of the access token.
  • AccountId: Copy this from the URL after you log into Basecamp:
    https://basecamp.com/<AccountId>
  • Schema: Set this to "V2" or "V3" to connect to Basecamp 2 or Basecamp 3 accounts.
  • ProjectId: For most table operations, a ProjectId is a required parameter. You can query the Projects table to obtain this value.

Using the Credentials for a Custom OAuth App

Create a Custom OAuth App

Creating a custom OAuth app is optional in the headless OAuth flow; you can skip creating an app by connecting with the cmdlet's embedded OAuth credentials. You might want to create a custom OAuth app to change the information displayed when users log into Basecamp to grant permissions to the cmdlet.

See Creating a Custom OAuth App for a procedure. You can then follow the procedures below to authenticate and connect to data.

Obtain a Verifier Code

Set the following properties on the headless machine:

  • InitiateOAuth: Set this to OFF.
  • OAuthClientId: Set this to the Client Id in your app settings.
  • OAuthClientSecret: Set this to the Client Secret in your app settings.
  • AccountId: Copy this from the URL after you log into Basecamp:
    https://basecamp.com/<AccountId>

You can then follow the steps below to authenticate from another machine and obtain the OAuthVerifier connection property.

  1. Call the GetOAuthAuthorizationURL stored procedure with the CallbackURL input parameter set to the exact Redirect URI you specified in your app settings.
  2. Open the returned URL in a browser. Log in and grant permissions to the cmdlet. You are then redirected to the callback URL, which contains the verifier code.
  3. Save the value of the verifier code. You will set this in the OAuthVerifier connection property.

On the headless machine, set the following connection properties to obtain the OAuth authentication values:

  • OAuthVerifier: Set this to the verifier code.
  • OAuthSettingsLocation: Set this to persist the encrypted OAuth authentication values to the specified file.
  • InitiateOAuth: Set this to REFRESH.
  • AccountId: Copy this from the URL after you log into Basecamp:
    https://basecamp.com/<AccountId>

After the OAuth settings file is generated, set the following properties to connect to data:

  • OAuthSettingsLocation: Set this to the file containing the encrypted OAuth authentication values. Make sure this file gives read and write permissions to the provider to enable the automatic refreshing of the access token.
  • InitiateOAuth: Set this to REFRESH.
  • AccountId: Copy this from the URL after you log into Basecamp:
    https://basecamp.com/<AccountId>
  • Schema: Set this to "V2" or "V3" to connect to Basecamp 2 or Basecamp 3 accounts.
  • ProjectId: For most table operations, a ProjectId is a required parameter. You can query the Projects table to obtain this value.

Transfer OAuth Settings

Follow the steps below to install the cmdlet on another machine, authenticate, and then transfer the resulting OAuth values.

On a second machine, install the cmdlet and connect with the following properties set:

  • OAuthSettingsLocation: Set this to a writable text file.
  • OAuthClientId: Set this to the client Id assigned when you registered your app.
  • OAuthClientSecret: Set this to the client secret assigned when you registered your app.
  • CallbackURL: Set this to the Redirect URI you specified in your app settings.
  • AccountId: Copy this from the URL after you log into Basecamp:
    https://basecamp.com/<AccountId>

Test the connection to authenticate. The resulting authentication values are written, encrypted, to the path specified by OAuthSettingsLocation. Once you have successfully tested the connection, copy the OAuth settings file to your headless machine. On the headless machine, set the following connection properties to connect to data:

  • InitiateOAuth: Set this to REFRESH.
  • OAuthSettingsLocation: Set this to the path to your OAuth settings file. Make sure this file gives read and write permissions to the cmdlet to enable the automatic refreshing of the access token.
  • AccountId: Copy this from the URL after you log into Basecamp:
    https://basecamp.com/<AccountId>
  • Schema: Set this to "V2" or "V3" to connect to Basecamp 2 or Basecamp 3 accounts.
  • ProjectId: For most table operations, a ProjectId is a required parameter. You can query the Projects table to obtain this value.

Copyright (c) 2020 CData Software, Inc. - All rights reserved.
Build 20.0.7587