...
- 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 evrytime everytime you check in in a hotel or a bar 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
- Some Ideas for marketing
- 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
...