Victor Aremu ahkohd

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.

Two way iframe communication

The main difference between the two pages is the method of sending messages. Recieving messages is the same in both.

Parent

Send messages to iframe using iframeEl.contentWindow.postMessage Recieve messages using window.addEventListener('message')

	/***
	* This script will anchor a GameObject to a relative screen position.
	* This script is intended to be used with ViewportHandler.cs by Marcel Căşvan, available here: http://gamedev.stackexchange.com/a/89973/50623
	* It is also copied in this gist below.
	*
	* Note: For performance reasons it's currently assumed that the game resolution will not change after the game starts.
	* You could not make this assumption by periodically calling UpdateAnchor() in the Update() function or a coroutine, but is left as an exercise to the reader.
	*/
	/* The MIT License (MIT)

	/**
	* Get a random floating point number between `min` and `max`.
	*
	* @param {number} min - min number
	* @param {number} max - max number
	* @return {number} a random floating point number
	*/
	function getRandomFloat(min, max) {
	return Math.random() * (max - min) + min;
	}

	/* CGSPrivate.h -- Header file for undocumented CoreGraphics stuff. */

	/* This file is a relicensed portion of DesktopManager and was originally released under
	* the terms of the GNU General Public Licence. Original licence text follows the new terms.
	* The contents of this file has been re-released by the original author under the following terms:
	*
	* Copyright (C) 2003, 2004, 2013 Richard J Wareham <richwareham@users.sourceforge.net>
	*
	* Permission is hereby granted, free of charge, to any person obtaining a copy of this
	* software and associated documentation files (the "Software"), to deal in the Software

	// Create our server
	var server;
	server = http.createServer(function(req,res){
	// Set CORS headers
	res.setHeader('Access-Control-Allow-Origin', '*');
	res.setHeader('Access-Control-Request-Method', '*');
	res.setHeader('Access-Control-Allow-Methods', 'OPTIONS, GET');
	res.setHeader('Access-Control-Allow-Headers', '*');
	if ( req.method === 'OPTIONS' ) {
	res.writeHead(200);

	/**
	* Like, basically PERFECT scrollbars
	*/

	/*
	It's pure CSS.
	Since a quick google search will confirm people going crazy about Mac OS Lion scrollbars...
	this has no fade-out effect.

	In Mac OS Lion, the lowest common denominator is always showing scrollbars by a setting.