- Taschenbuch: 78 Seiten
- Verlag: O'Reilly and Associates; Auflage: 1 (1. April 2012)
- Sprache: Englisch
- ISBN-10: 1449311601
- ISBN-13: 978-1449311605
- Größe und/oder Gewicht: 17,8 x 0,4 x 23,3 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 74.866 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Getting Started with OAuth 2.0 (Englisch) Taschenbuch – 1. April 2012
|Neu ab||Gebraucht ab|
Wird oft zusammen gekauft
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Über den Autor und weitere Mitwirkende
Ryan Boyd is a developer advocate at Google focused on enabling developers to extend Google Apps and build businesses on top of Google technology. He previously worked on OpenSocial and led the developer relations team for Google s AtomPub APIs. Prior to joining Google, Ryan worked in higher education as a web architect for RIT s central web hosting environment and as web app developer building admissions and student systems."
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
If you are new to this concept, you will still be confused after reading this. The author is not a good teacher, and the presentation style is very formal and technical. The diagrams are not really useful. You can definitely tell this was written by a highly technical person.
The examples are written in PHP. If you use a different language (VS C# or VB), you'll need to translate it on your own.
Most of the information in this book can be found online in the exact same technical format.
I already knew some things about OAuth and just needed a refreshed, so I got what I needed from it. But a "Getting Started" book should be a lot clearer and easier for anyone (with NO experience in the topic) to read and pick up the concepts quickly. This book fails in that regard.
This is where this book comes in. In about 60-70 pages it clarifies the current situation. It starts providing a historical introduction to the protocol and how it's related with initiatives pre-OAuth 1.0 and with OAuth 1.0 itself (removal of proprietary technologies, improved security). You'll learn the rationale behind this revision (new client profiles in particular) and some of the key features still under discussion. In particular "signatures", where Eran Hammer, the protocol editor, is openly opposed to not including them (and after reading his thoughts, I think he's right).
One chapter I specially loved is the one dedicated to OpenID Connect, the next evolution of OpenId. I've seen developers confused about the differences between OAuth (authorization) and OpenID (authentication) and this book differentiates them well. Interestingly, although they still keep different purposes, the new OpenID Connect will now be developed on top of OAuth-which makes sense, as you'll find out in the book.
Where the book falls short in my opinion (and the reason for losing one star) is in providing better guidance for developers willing to be authorization servers and not just clients of the protocol. OAuth 2.0 will only be successful if all API providers are able to implement it (big and small) and that's where this book could have done a better job. For example, recommending some web frameworks capable of OAuth 2.0 in Chapter 8 ("Tools and Libraries").
"Getting Started with OAuth 2.0" by Ryan Boyd is an easy read that answers right questions (like what's new in 2.0? which are the new client profiles? when should I use each one? what do I do if the access token expires or gets revoked?) and then can also be used as a simple reference of the workflows when you're actually implementing your app.
I'd recommend this book if you are new to OAuth and want to read it on a flight. Otherwise, there are online resources that are just as useful. For example, Google's Using OAuth 2.0 to Access Google APIs seems to cover almost as much content as this book.