You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Innovation Tagline:  (decentralization of central Identity Provider)

Project Keywords:  TBA

Project Members

  1. Roman Zoun Dr.-Ing. Roman Zoun
  2. Michel Sahli Michel 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 awareness in users and 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".


Image

Source: https://twitter.com/SSI_by_memes

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 advertisement around Linux foundation. 

Solution

  1. Provide a service which combines the usual social login onboarding, without the central IDP get your behavior. We introduce the Social verifiable credential, a service where a user login once, and issue his social account as verifiable credentials in his wallet. In addition we introduce a simple OIDC SSI verifier to include the social login as verifiable credentials easy into your service. 
  2. Our solution doesn't include any central IDP, no databases for storing the data and is easy to integrate to your service, as configuration for docker-compose, kubernetes AWS, Azure, Google Cloud ...
  3. As minimum is an issuer with the social login via central IDP. The verifier is not needed in the beginning, since a lot of products can solve this

Accomplishment and Team

  • 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,
    • Google Verifiable Credetnial schema
    • Facebook Verifiable Credetnial schema
    • Twitter Verifiable Credetnial schema
    • ...
  • implement platform with at least one social login (first google, then facebook, twitter, linkedIn, Apple, GitHub WeChat, amazon, etc),
    • Spring Security Client with google IDP configuration
  • 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),
    • Spring Backend
    • Spring Webhook, Aries cloud wallet for issuing and communication with user wallet
    • Angular frontend
  • Start marketing for OIDC-Verifier and easy tutorials how to integrate with videos, twitter, with help of hyperledger
    • Some Ideas for marketing
      • Target Services: Create Video describing architecture and how central idp is working 
      • Target users: Create funny sketches how would it be if your wife/mama/dad would be like central IDP and know everytime you check in in a hotel or a bar or club 
      • Target Services: Create Architecture Video for decentralization of central IDP and the service still can save the data in the service, and for the service it doesn't have any negative aspects
      • Target users: Same funny video how with the wife/mama/dad, but this time she only knows, you go to a friend, but doesn't know what you did next
    • Share via twitter etc
  • implement OIDC-verifier with configuration for the credential definition ids of the social login
    • Spring athorization server + Spring Webhook + Aries cloud wallet 
    • configured on credential definition ids of the Verifiable credentials that are implemented on the platform 
    • Login page is QR code with proof request for this
  • implement different ops configs, for Premis, Cloud, Proxy etc


Risk

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
  • Another Risk is that one social provider blocks us
    • Limit risk by instant marketing reactions around this, and starting petitions, and ask all known GPDR data protection auditors to look at this...we can't do other things




  • No labels