This document discusses OAuth and the Doorkeeper gem. It explains the roles in OAuth of the resource owner, resource server, authorization server, and client. It outlines the four OAuth flows: authorization code, implicit, resource owner password credentials, and client credentials. It then introduces Doorkeeper as a Ruby gem for implementing OAuth in Rails applications and provides references for more information on Doorkeeper and OAuth flows.

1. OAuth con Doorkeeper
Sergio Marín
@highercomve

3. ¿Por qué usar Oauth?

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

7. OAuth / Roles
● Resource Owner (User)
● Resource Server (API)
● Authorization Server (~ API )
● Client (Application)

9. 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.

10. OAuth / Flows
● Authorization Code
● Implicit
● Resource Owner Password Credentials
● Client Credentials

11. OAuth / Flows

12. OAuth / Flows

13. OAuth / Flows

16. Ahora hablemos de Doorkeeper
https://github.com/doorkeeper-gem/doorkeeper

18. Vamos al código

19. Doorkeeper
Repositorio de la presentación:
https://github.com/highercomve/oauth_con_doorkeeper

20. OAuth / referencias
https://github.com/doorkeeper-gem/doorkeeper/wiki
https://github.com/doorkeeper-gem/doorkeeper/wiki/Client-Credentials-flow
https://github.com/doorkeeper-gem/doorkeeper/wiki/authorization-flow
https://github.com/doorkeeper-gem/doorkeeper/wiki/Using-Resource-Owner-
Password-Credentials-flow
https://github.com/doorkeeper-gem/doorkeeper/wiki/Create-a-OmniAuth-
strategy-for-your-provider
https://github.com/plataformatec/devise/wiki/OmniAuth:-Overview