Phong Thieu pthieu

OAUTH2

The Problem

I’m a web app that wants to allow other web apps access to my users’ information, but I want to ensure that the user says it’s ok.

The Solution

I can’t trust the other web apps, so I must interact with my users directly. I’ll let them know that the other app is trying to get their info, and ask whether they want to grant that permission. Oauth defines a way to initiate that permission verification from the other app’s site so that the user experience is smooth. If the user grants permission, I issue an AuthToken to the other app which it can use to make requests for that user's info.

Note on encryption

Oauth2 has nothing to do with encryption -- it relies upon SSL to keep things (like the client app’s shared_secret) secure.

	# best practice: linux
	nano ~/.pgpass
	:5432::username:password
	chmod 0600 ~/.pgpass

	# best practice: windows
	edit %APPDATA%\postgresql\pgpass.conf
	:5432::username:password

	# linux

	#!/bin/sh

	# Make sure to:
	# 1) Name this file `backup.sh` and place it in /home/ubuntu
	# 2) Run sudo apt-get install awscli to install the AWSCLI
	# 3) Run aws configure (enter s3-authorized IAM user and specify region)
	# 4) Fill in DB host + name
	# 5) Create S3 bucket for the backups and fill it in below (set a lifecycle rule to expire files older than X days in the bucket)
	# 6) Run chmod +x backup.sh
	# 7) Test it out via ./backup.sh

	#!/bin/bash

	# Performs a dump of target database and compresses result.
	# Outputs to: $DUMPDIR/$DUMPNAME.tar.xz

	# Note: Absolute paths are required for use in cron jobs

	DBNAME=meteor
	ROOTDIR=/Users/alanning/foo
	DUMPDIR=$ROOTDIR/dumps