Re: Google signin

From: Greg Stark <stark(at)mit(dot)edu>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: Google signin
Date: 2017-07-12 14:16:40
Message-ID: CAM-w4HMqJN4rS0p3hJ+0BkP78NR6VorLxYfNmNqB0NAebCtzKA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On 12 July 2017 at 13:23, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> I've attached a screenshot of what the implementation looks like at this
> point. Obviously, CSSing and things can always be improved.

The main point of this would be to not have a new password so I find
it strange that there's still a password field at all. Maybe this is
just the CSSing you describe if you styled it so there were two
options, "log in with password" and "log in with Google" and they were
obviously two independent options. The other option with broad
coverage would be Facebook, but for our community github is also
tempting (Is OpenID still a thing?).

The big question though is whether to still require a community id at
all. If we just let anyone log in via Google and create a placeholder
account on demand if one doesn't exist then you shouldn't have to go
through the "create an account" step at all. And you shouldn't have to
remember a new userid at all.

--
greg

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2017-07-12 14:27:57 Re: Google signin
Previous Message Dave Page 2017-07-12 13:53:11 Re: Supported Windows version for the Windows installer