OAuth

OAuth

OAuth2 simplified

• The Third-Party Application: "Client"
  • The client is the application that is attempting to get access to the user's account
  • It needs to get permission from the user before it can do so
• The API: "Resource Server"
  • The API server used to access the user's information
• The Authorization Server
  • The server that presents the interface where the user approves or denies the request
• The User: "Resource Owner"
  • The person who is giving access to some portion of their account
• Authorization
  • The first step of OAuth 2 is to get authorization from the user

Build a Node API with OAuth

• The promisify function of util lets you take a function that expects a callback and instead will return a Promise
• Sequelize to define your database schema
  • Once you’ve created the database, you can define the schema for it using database.define for each table
• Epilogue to create some REST API endpoints with near-zero boilerplate
  • epilogue.initialize({ app, sequelize: database }) npm install sequelize@4.38.0 epilogue@0.7.1 sqlite3@4.0.2
• Create an Authorization Server
  • Okta can act as an authorization server to allow you to secure your data
  • Okta is a cloud service that allows developers to create, edit, and securely store user accounts and user account data, and connect them with one or multiple applications

OAuth Wiki

• OAuth is 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

Additional Resources:

• Google OAuth2 docs
• Google openid docs
• Google OAuth server side