Re: [pgsql-www] Google signin
| От | Magnus Hagander |
|---|---|
| Тема | Re: [pgsql-www] Google signin |
| Дата | |
| Msg-id | CABUevEya3hKxgY5CwBbJf6oV9tGe0Zs=y-UCxiOqv+pyRo5naQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [pgsql-www] Google signin (Magnus Hagander <magnus@hagander.net>) |
| Ответы |
Re: [pgsql-www] Google signin
Re: [pgsql-www] Google signin |
| Список | pgsql-www |
On Wed, Jul 12, 2017 at 4:37 PM, Magnus Hagander <magnus@hagander.net> wrote:
On Wed, Jul 12, 2017 at 4:35 PM, Greg Stark <stark@mit.edu> wrote:On 12 July 2017 at 15:27, Magnus Hagander <magnus@hagander.net> wrote:
>
> That said, this is not intended to *replace* the username/password login
> part, it would be in addition to it.
In that case I think it's actively a bad idea. If people would still
have to create another password there's no point and it would
contribute to people not wanting to use common auth schemes like this.They would not have to make another password. It would be possible to create a community account without a password (which would then only be reachable through an oauth login from a supported provider).If you just have to make a username that's not as bad (though not ideal).That would be the idea.
So to show it in more detail, here is an example of the workflow of my prototype: https://www.hagander.net/tmp/flow.ogv
(note for those reading in the archives -- link will go dead in a couple of days)
В списке pgsql-www по дате отправления: