OAuth con DoorkeeperSergio Marín

@highercomve

¿Por qué usar Oauth?

Magia

¡Hay que implementar una solución para mañana!

OAuth / Roles

● Resource Owner (User)● Resource Server (API)● Authorization Server (~ API )● Client (Application)

https://www.digitalocean.com/community/tutorials/an-introduction-to-oauth-2

OAuth / Supuestos

Por lo tanto para que el protocolo pueda funcionar necesitamos, registrar nuestra APP (Client) en el Authorization Server

Y el usuario debe pertenecer al API, es decir, el usuario debe estar registrado.

OAuth / Flows

● Authorization Code● Implicit● Resource Owner Password Credentials ● Client Credentials

OAuth / Flows

OAuth / Flows

OAuth / Flows

Ahora hablemos de Doorkeeper

https://github.com/doorkeeper-gem/doorkeeper

Vamos al código

Doorkeeper

Repositorio de la presentación:

https://github.com/highercomve/oauth_con_doorkeeper

OAuth / referencias

https://github.com/doorkeeper-gem/doorkeeper/wikihttps://github.com/doorkeeper-gem/doorkeeper/wiki/Client-Credentials-flowhttps://github.com/doorkeeper-gem/doorkeeper/wiki/authorization-flowhttps://github.com/doorkeeper-gem/doorkeeper/wiki/Using-Resource-Owner-Password-Credentials-flowhttps://github.com/doorkeeper-gem/doorkeeper/wiki/Create-a-OmniAuth-strategy-for-your-providerhttps://github.com/plataformatec/devise/wiki/OmniAuth:-Overview