Java Reference
In-Depth Information
Now when your application loads, if users have not authenticated, they will see the
sign-in page shown in Figure 6-2 as opposed to your timecard UI if they have already
signed in.
Figure 6-2. The Google Accounts sign-in page for your application
Summary
This chapter demonstrated how quick and easy it is to implement authentication
for your timecard application using Google Accounts. The service offers role-based
security to your application as well as individual directories.
App Engine is flexible and does not require you to use Google Accounts for
authentication if it's not the best fiat for your application. If you need more granular
security with customized permissions, you are free to develop your own framework
using custom classes, tables, and memcache. However, doing so eliminates some of
the development benefits that you get for free with Google Accounts.
 
Search WWH ::




Custom Search