On Thu, Sep 25, 2014 at 5:03 AM, Daniel Guillamot whilet...@gmail.com
wrote:
Do you think using Google Accounts is a reasonable user authentication
system for a GAE application?
Should I require all my users to have Google Accounts for certain
functions (commenting, and other user generated
Do you think using Google Accounts is a reasonable user authentication
system for a GAE application?
Should I require all my users to have Google Accounts for certain functions
(commenting, and other user generated content).
Or, should I create my own system. Users have to create user ids,
Hi there,
I have been using Google Accounts for my primary project. Here are pros and
cons based on my experience.
pros:
1. You do not deal with lost passwords
2. You ride the innovation of Google, e.g. 2-factor authentication etc that you
might not be able to afford and are very costly if you
Those are good lists.
One more: If your customers are business users, google accounts won't work.
Because people don't want to use their personal account for work stuff. And
they are afraid to set up a google account wrapper around their work email
address, because ordinary humans don't
I'm using the built in users authentication on my website. I really
like it's simplicity, and I like the fact that many potential users
will already have a Google Account, so they can use my site without
having to create a new account.
But I've run into a problem. I'd like to have protected
Does it make sense for developers to tie their apps into Google
Accounts and if so, why?
Or put another way, what are the pros and cons of tying an app into
Google Accounts?
Thx.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
Is anyone else getting:
Sorry, there seems to be a problem. The service you're looking for is
temporarily unavailable. We're working hard to restore your access as
soon as possible. Please try again in a few hours. Thanks for your
patience.
While trying to sign in to their App Engine app?
