Docs

Generic OAuth 1.0 and 2.0 Examples

The recommended method for creating custom Social Connections is to use Auth0's Custom Social Connections Extension. The information in this article should be used for reference purposes only.

Adding OAuth 1.0 and OAuth 2.0 providers as Connections allow you to support providers that are not currently built-in to the Auth0 Management Dashboard, like DigitalOcean, Tumblr, and more.

This document covers examples of OAuth 1.0/2.0 Connections that you can create by making the appropriate POST call to the Auth0 APIv2's Connections endpoint. Please note that doing so requires an APIv2 token with create:connections scope.

DigitalOcean

  1. Navigate to Digital Ocean.
  2. If you have not already registered a Digital Ocean application, you will need to do so prior to continuing.
  3. Once available, copy the Client ID and Client Secret for use with your cURL POST.



Dribbble

  1. Navigate to Dribble.
  2. If you have not already registered a new Dribble consumer, you will need to do so prior to continuing. If you have, set the Redirect URI of your application to https://YOUR_DOMAIN/login/callback.
  3. Copy the Client ID and Client Secret for use with your cURL POST.



Imgur

  1. Navigate to Imgur.
  2. If you have not already registered an Imgur application, you will need to do so prior to continuing.
  3. Once available, copy the Client ID and Client Secret for use with your cURL POST.



JIRA

Step 1: Generate an RSA Keypair

Generate an RSA keypair with the following command (or any equivalent method):

From JIRA, go to Administration > Application > Application Links, and create an Application Link with the following settings:

  • Application URL: Any arbitrary URL (you can ignore the No response was received from the URL warnings);
  • Application Name: Any arbitrary name;
  • Application Type: Generic Application;
  • Create incoming link: checked.

Leave all other options left blank.

To create the incoming link, use the following settings:

  • Consumer Key: Any arbitrary URL-friendly name (for example, auth0-jira)
  • Consumer Name: Any arbitrary name
  • Public Key: The RSA keypair previously generated in step 1 (copy and paste the entire .pub file)
  • Consumer Callback URL: https://YOUR_DOMAIN/login/callback

Updating Settings

If you need to modify these settings after you've created the application link, you can do so via the Incoming Authentication section of the link's settings.

In the JSON below, replace all instances of the following placeholders:

  • JIRA_URL: The root URL of your JIRA instance (for example, https://foo.atlassian.net)
  • CONSUMER_KEY: The chosen Consumer Key for your application link
  • CONSUMER_SECRET: The previously generated private key (as a JSON string). You can convert EXAMPLE.key to a valid JSON string using the following command:



Tumblr

  1. Navigate to Tumblr.
  2. If you have not already registered a new Tumblr application, you will need to do so prior to continuing.
  3. Copy the OAuth Consumer Key and Secret Key for use with your cURL POST.



Twitch

  1. Navigate to Twitch.
  2. If you have not already registered a Twitch application, you will need to do so prior to continuing.
  3. Once available, copy the Client ID and Client Secret for use with your cURL POST.



Uber

  1. Navigate to Uber Developers.
  2. If you have not already registered an Uber application, you will need to do so prior to continuing. If you have, set the Redirect URI of your application to 'https://YOUR_DOMAIN/login/callback'.
  3. Copy the Client ID and Client Secret for use with your cURL POST.



Vimeo

  1. Navigate to Vimeo.
  2. If you have not already registered a new Vimeo application, you will need to do so prior to continuing.
  3. Copy the Client ID and Client Secret for use with your cURL POST.



Xing

  1. Navigate to Xing.
  2. If you have not already registered a Xing application, you will need to do so prior to continuing.
  3. Once available, copy the Client ID and Client Secret for use with your cURL POST.