Versions Compared

Old Version 1

changes.mady.by.user Dr.-Ing. Roman Zoun

Saved on

compared with

New Version 2

changes.mady.by.user Dr.-Ing. Roman Zoun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Innovation Tagline:  TBA  (decentralization of central Identity Provider)

Project Keywords:  TBA

Project Members

  1. Roman Zoun Dr.-Ing. Roman Zoun
  2. TBAMichel Sahli
  3. TBA

Project Description (no more than 1,000 words including graphics)

I register myself on linux foundation using linkedIn and now I got advertisement of training on linux foundation platform. Imagine to "login with google" and google will never know you did it. We introduce an anonymous social login plugin to digital services to allow users use the secure way to onboard and register using thirdparty login, without notice them about it. Our goal is to wake the privacy awerness awareness in users and move tell the world, that social login can be anonymous and the data collected by them shouldn't be collected. Stop "login with google", start "login with google as verifiable credential".

Problem

  1. Onboarding processes are established on nearly every online service using social login via OIDC This is easy, but involves a central identity provider such as LinkedIn Facebook google etc, see this:
  2. The current solution is user friendly and everyone love to use it, mostly with an two factor authentication, which involves often the mobile phone and a password. 
  3. The social login is integrated in the process like start-button on windows desktop, but everytime I use it, the central IDP notice this and can learn more about the behavior of the user. For example, I logged in here using linkedIn, so LinkedIn will provide me some advertisment arount linux foundation. 

...

  • We are currently only one person with some tech background and architecture with hyperledger aries 0.6/Spring/angular
  • more dev skills are required backend + frontend

Project Plan

Project plan

  • Define schemas,
  • implement plattform platform with social logins, at least one social login (first google, then facebook, twitter, linkedIn, Apple, GitHub WeChat, amazon, etc),
  • implement self-issuer service, which means the user see his data after login and then can issue it to his wallet (Evernym/lissi/trinsic/esatus),
  • Start marketing for OIDC-Verifier and easy tutorials how to integrate with videos, twitter, with help of hyperledger
  • implement OIDC-verifier with configuration , for the credential definition ids of the social login
  • implement different ops configsTBA, for Premis, Cloud, Proxy etc


Risk

  • The risk is, that no one will integrate the OIDC-Verifier, because of the effort (chicken egg problem)
    • We reduce the risk by providing a lot of tutorials and support to integrate the OIDC verifier
    • OIDC-Verifier is free, and we say that other products of trinsic, esatus, evernym can be used here
  • another risk is the scalability of user access, what if it goes to the moon, we are not sure about the scalability of the aries wallet
    • we reduce it, by hyperledger community support for production ready deployment of cloud wallet
  • Another risk, is that users will not use it (chicken egg problem)
    • We need at least on hyperledger/linux foundation the possibility to login with it, then we will make marketing to show the data privacy benefits for the user
    • hope it begins with some enthusiasts but will scale later to everyone
    • Since this is something that users get into SSI, we are sure, we get marketing support of SSI companies and enthusiasts