Chapter 3Authorizing Your Glassware
In Chapter 2, The Google App Engine PaaS, we set up a simple Google App Engine (GAE)–hosted Glassware shell. But it wasn’t Glassware because it could never run on Glass. To do so requires authorization. Authorization is required to both flag an application as real Glassware and interact with a user on a personal level, such as by inserting cards directly into a user’s timeline.
Whereas authentication is about verifying who a user is, authorization is fundamentally about user experience. Formal definitions cite security and access control, but our purpose for authorization is to uniquely identify the correct user to customize his experience in some way by accessing and sometimes managing his data.
In this ...
Get Programming Google Glass now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
