Dmytro Bartieniev kuhelbeher

Про токены, JSON Web Tokens (JWT), аутентификацию и авторизацию. Token-Based Authentication

Last major update: 25.08.2020

Что такое авторизация/аутентификация
Где хранить токены
Как ставить куки ?
Процесс логина
Процесс рефреш токенов
Кража токенов/Механизм контроля токенов

The Problem

Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)

The temptingly easy but ultimately wrong solution:

Alter the port the script talks to from 8000 to 80:

}).listen(80);

	//return an array of objects according to key, value, or key and value matching
	function getObjects(obj, key, val) {
	var objects = [];
	for (var i in obj) {
	if (!obj.hasOwnProperty(i)) continue;
	if (typeof obj[i] == 'object') {
	objects = objects.concat(getObjects(obj[i], key, val));
	} else
	//if key matches and value matches or if key matches and value is not passed (eliminating the case where key matches but passed value does not)
	if (i == key && obj[i] == val \|\| i == key && val == '') { //