- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Thu, 17 Dec 2015 14:09:07 +0100
- To: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Cc: public-webapps <public-webapps@w3.org>
- Message-ID: <CAKaEYh+OkwysCw+KA+d=L75V1QNMimLAA6frmAnojqQ5Xox0VA@mail.gmail.com>
On 17 December 2015 at 13:26, Stian Soiland-Reyes < soiland-reyes@cs.manchester.ac.uk> wrote: > Excerpts from Binyamin's message of 2015-12-12 19:50:31 +0000: > > Currently many apps uses SSO (Single sign-on, > > https://en.wikipedia.org/wiki/Single_sign-on) with different APIs and > > protocols. It still requires server-side authentications. > > Browsers/OSs has to validate the main personal identification data > > (email/phone). Share the data after user acceptation similar to other > APIs > > like Geolocation API (demo http://html5demos.com/geo). > > I am only wondering if it in any way could be used in save way as a > Signin > > authentication? Maybe by uses some encrypted validation key? > > You'll probably be interested to read about WebID: > > http://www.w3.org/2005/Incubator/webid/spec/ > > FOAF+SSL is probably also relevant: > > http://www.w3.org/wiki/Foaf+ssl FYI foaf + ssl was rebranded to be called webid: http://webid.info/ It's now being used to power the Solid platform, I made a small gitbook with more details https://melvincarvalho.gitbooks.io/solid/content/ IMHO this is identity and the decentralized web done right. Whether anyone really still wants decentralization, I dont really know. But I'll certainly want to use it. > > > and obviously OAuth: > > http://oauth.net/ > > > -- > Stian Soiland-Reyes, eScience Lab > School of Computer Science > The University of Manchester > http://soiland-reyes.com/stian/work/ > http://orcid.org/0000-0001-9842-9718 > >
Received on Thursday, 17 December 2015 13:09:36 UTC