Modern Authentication

A Non-Dystopian Look At

Ado Kukic

Developer Evangelist

Auth0

@kukicado

Authentication Used to be Easy*

* Not really

@kukicado

{ username / password }

{ sid 123 }

@kukicado

{ sid 123 }

{ html }

@kukicado

Modern Auth is Complex

Grant Types

Platforms

Auth Flows

@kukicado

4 Types of Authentication

Web

API

SPA

Native

@kukicado

OAuth 2.0

An open standard for access delegation, commonly used as a way for Internet users to grant websites or applications access to their information on other websites but without giving them the passwords.

An open standard for access delegation.

@kukicado

OAuth 2.0 Roles

Resource Owner

The entity that can grant access to a protected resource. Typically this is the end-user.

Resource Server

The server hosting the protected resources. This is the API you want to access.

Client

The app requesting access to a protected resource on behalf of the Resource Owner.

Authorization Server

The server that authenticates the Resource Owner, and issues tokens.

OAuth 2.0 Endpoints

Authorization

Used to interact with the resource owner and get the authorization to access the protected resource.

Token

Used by the application in order to get an Access Token or a Refresh Token.
(Not used in Implicit Flow)

@kukicado

Authorization Code vs

Access Token vs Refresh Token vs Id Token

Authorization Code

An opaque string, meant to be exchanged with an Access Token at the token endpoint.

Access Token

An opaque string or JWT that denotes who has authorized which permissions (scopes) to which application.

Refresh Token

A special kind of token containing the information required to obtain a new Access Token or ID Token.

Id Token

A JWT that contains user profile information (name, email, etc.), represented in the form of claims.

@kukicado

OAuth 2.0 Flows

Authorization Code

Authorization Code with Proof Key for Code Exchange (PKCE)

Implicit

Client Credentials

@kukicado

Traditional

Web Application

Authorization Code Flow

@kukicado

Baseline

{ html }

@kukicado

/callback?code={123}

{ tokens }

{ sid 123 }

Authentication

@kukicado

{ html }

Authenticated

@kukicado

{ ok }

{ success }

{ change pw }

User Changes

@kukicado

API

Backend

Client Credentials Grant Flow

@kukicado

Baseline

{ json }

@kukicado

Authentication

@kukicado

Authenticated

{ json }

@kukicado

Refresh Token

@kukicado

Getting New Access Token

{ json }

@kukicado

SPA

Single Page Application

Implicit Grant Flow

@kukicado

Baseline

{ json }

@kukicado

Authentication

@kukicado

Authenticated

{ json }

@kukicado

Silent Authentication

{ json }

@kukicado

Silent Authentication

{ json }

iframe

@kukicado

Native

Android, iOS, Desktop

Authorization Code with PKCE Grant Flow

@kukicado

Baseline

{ json }

@kukicado

Authentication

{ code_challenge }

code={123}

@kukicado

Authentication

{ code={123} code_verifier }

@kukicado

Authenticated

{ json }

@kukicado

Summary

@kukicado

Modern authentication is complex.

OAuth 2.0 offers solutions / flows for most use cases.

Implementing OAuth 2.0 can provide a competitive advantage.

Resources

@kukicado

OAuth 2.0 Official Website

https://oauth.net/2/

OAuth 2.0 Complete Guide

http://bit.ly/oauth-complete

OAuth 2.0 Scopes

http://bit.ly/oauth-scopes

Thank You!

@kukicado

http://bit.ly/modern-auth-dallas