HTML and CSS Reference
In-Depth Information
OAuth provides a great way to get everything we need:
Verify that the person is indeed real: We can reasonably assume that anyone who is signed
into a valid Facebook or Twitter account is a real person.
Collect necessary data about the user: For this app, we would really only need a name
and e-mail.
Reduce the barrier to entry: By eliminating all the usual steps of creating an account, we
could get the user into our app in seconds with just two clicks.
What Role Does It Play?
OAuth would be the gatekeeper for our app. It would use third-party services to verify the authenticity of a user and
gather the necessary information for the app to function.
How Does It Work?
You'll find more details on the specifics of OAuth in Appendix A, but at its core, OAuth contacts the service through
which we want to authenticate our user and sends a token identifying our app. The user is prompted to log in to the
third party service if they're not already and then allow or deny the requested privileges from our app. If the user
allows our app to access the requested data, the service sends back a token we can use to retrieve the necessary data
and consider a user “logged in” to our app.
At this point, we have successfully defined a rough list of functionality and requirements for our app. We also used that
information to flesh out a list of tools we will use to bring the app to life.
In the next chapter, you'll get familiar with Pusher and its underlying technologies, and you'll build your first
realtime application.
Search WWH ::

Custom Search