* Not really
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
{ username / password }
{ sid 123 }
@kukicado
http://bit.ly/auth0-winnipeg
{ sid 123 }
{ html }
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
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
http://bit.ly/auth0-winnipeg
An authentication layer built on top of OAuth 2.0, allowing clients to verify the identity of an end-user based on the authentication performed by an authorization server.
@kukicado
An authentication layer built on top of OAuth 2.0
http://bit.ly/auth0-winnipeg
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.
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
http://bit.ly/auth0-winnipeg
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
http://bit.ly/auth0-winnipeg
Authorization Code
Authorization Code with Proof Key for Code Exchange (PKCE)
Implicit
Client Credentials
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
{ html }
@kukicado
http://bit.ly/auth0-winnipeg
/callback?code={123}
{ tokens }
{ sid 123 }
@kukicado
http://bit.ly/auth0-winnipeg
{ html }
@kukicado
http://bit.ly/auth0-winnipeg
{ ok }
{ success }
{ change pw }
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
{ json }
{ json }
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
{ json }
{ json }
@kukicado
http://bit.ly/auth0-winnipeg
{ json }
{ json }
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
* Up until now
{ json }
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
{ json }
{ json }
@kukicado
http://bit.ly/auth0-winnipeg
{ json }
{ json }
@kukicado
http://bit.ly/auth0-winnipeg
{ json }
{ json }
iframe
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
http://bit.ly/auth0-winnipeg
{ json }
@kukicado
http://bit.ly/auth0-winnipeg
{ code_challenge }
code={123}
@kukicado
http://bit.ly/auth0-winnipeg
{ code={123} code_verifier }
@kukicado
http://bit.ly/auth0-winnipeg
{ json }
{ json }
@kukicado
http://bit.ly/auth0-winnipeg
@kukicado
Modern authentication is complex.
OAuth 2.0 offers guidance for most use cases.
Implementing OAuth 2.0 can provide a competitive advantage.
http://bit.ly/auth0-winnipeg
@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
http://bit.ly/auth0-winnipeg
http://bit.ly/auth0-winnipeg