Managing Virtual Connectors for Collections

Overview

In this article, we will define how to create various connectors for a Virtual Collection, and provide a few of the more common endpoint configurations.

As more authentication modes become available they will be added to this document.

Note: If you are using Zendesk, Salesforce, or Jira Service Desk as one of your connected data sources for a Virtual Collection, you must first follow these instructions for setting it up in Salesforce, Zendesk, or Jira Service Desk

OAuth2:

• Define a connector name, description, and select OAuth2
  
  
  
  
• Configure the OAuth2. You can connect to any application which supports OAuth2 application integration. 

The example below shows the configuration for a Salesforce connection.

• Test your connector configuration to make sure it is successfully defined.
  Since the oAuth2 is authentication is performed on the source system, a new window will open to enter your authentication credentials.
• Add the new connector by clicking “Add Connector” button.
• You can edit existing connectors from this dialog (do not forget to save the edited connector before closing the dialog).
• If a connector is not in use, you can delete it.

Two common connection types for a Virtual Connector are SFDC and Zendesk.  Below are connector details for each.  Additional connectors will be documented here.

SFDC

Production Salesforce Connector Details

• Type: OAuth2
• Client ID: Consumer Key from SFDC App 
• Client Secret: Consumer Secret from SFDC App 
• Scope: OAuth Scopes from SFDC App
• Authorization Endpoint : https://login.salesforce.com/services/oauth2/authorize
• Token Endpoint : https://login.salesforce.com/services/oauth2/token
• Redirect URI: https://app.totango.com/auth/das/callback 

Sandbox Salesforce Connector Details

• Type: OAuth2
• Client ID: Consumer Key from SFDC App
• Client Secret: Consumer Secret from SFDC App
• Scope: OAuth Scopes from SFDC App
• Authorization Endpoint : https://test.salesforce.com/services/oauth2/authorize
• Token Endpoint : https://test.salesforce.com/services/oauth2/token
• Redirect URI: https://app.totango.com/auth/das/callback 

Note:  If you are using a custom domain and are preventing login from test.salesforce.com or login.salesforce.com your Token Endpoint and Authorization Endpoint should reflect the correct domain.

Zendesk

Zendesk Connector Details

• Type: OAuth2
• client_id: Client Name from Zendesk OAuth client Client Name
• client_secret: Secret from Zendesk OAuth client
• scope: read
• Authorization Endpoint : https://[your_sub_domain].zendesk.com/oauth/authorizations/new
• Token Endpoint : https://[your_sub_domain].zendesk.com/oauth/tokens
• Redirect URI: https://app.totango.com/auth/das/callback

Jira Service Desk

Jira Service Desk Connector Details

• Type: OAuth2
• client_id: Client ID from Jira Connected App details
• client_secret: Secret from Jira Connected App details
• scope: read:jira-work
• Authorization Endpoint : https://auth.atlassian.com/authorize?audience=api.atlassian.com&prompt=consent
• Token Endpoint : https://auth.atlassian.com/oauth/token
• Redirect URI: https://app.totango.com/auth/das/callback