Mahdi Yusuf myusuf3

The more OAuth providers there are, the more inconsistency there is. Not following the specification puts an increased and unnecessary burden on the developer.

In the past couple of weeks I have coordinated and authenticated with more than my fair share of OAuth providers. That being said, you should be thinking "Hey, isn't OAuth a specification?" Once you do one you should be simply swapping out keys and urls and you should be good to go right? So wrong.

Follow the specification and be consistent.

This article is meant to let the OAuth providers know some of the pain points of dealing with them as providers and steps they could take to make interacting with their API a joy.

API Documentation

GitHub OAuth Busy Developer's Guide

This is a quick guide to OAuth2 support in GitHub for developers. This is still experimental and could change at any moment. This Gist will serve as a living document until it becomes finalized at Develop.GitHub.com.

OAuth2 is a protocol that lets external apps request authorization to private details in your GitHub account without getting your password. All developers need to register their application before getting started.

Web Application Flow

Redirect to this link to request GitHub access:

	#!/bin/bash

	# Curl and run this script as part of your .travis.yml before_script section:
	# before_script:
	# - curl https://gist.github.com/santiycr/5139565/raw/sauce_connect_setup.sh \| bash

	CONNECT_URL="http://saucelabs.com/downloads/Sauce-Connect-latest.zip"
	CONNECT_DIR="/tmp/sauce-connect-$RANDOM"
	CONNECT_DOWNLOAD="Sauce_Connect.zip"
	READY_FILE="connect-ready-$RANDOM"

	for k,v in propertyDict:
	for k1,v2 in propertyDict[k]:
	print('---' + k1 + '---' + propertyDict[k][k1])