Self Issued OpenId Provider (SIOP) for Decentralized Identities (DIDs) allows integration of Identity Wallets with Relying Parties which uses OpenIDConnect Clients (OIDC Clients).
Here we look at the emerging integration between OpenID Connect and the world of DIDs and self-sovereign identity.
- https://didsiop.org/
# Identity, Unlocked - podcast
In this episode of Identity. Unlocked, principal architect at Auth0 and podcast host, Vittorio Bertocci, focuses on the Self-Issued OpenID Provider specification, also known as SIOP.
We are joined today by Kristina Yasuda, Identity Standards Architect at Microsoft and longtime advocate of decentralized identity- listen 
https://www.listennotes.com/e/p/769e283301004ff0896fd58b04a29815/ SIOP with Kristina Yasuda
# Implementations This implements Self Issued OpenId Connect Provider (SIOP) for Decentralized Identities (DIDs).
This is implemented as a browser add-on and allows to integrate Identity Wallets with Relying Parties which uses OpenIDConnect Clients (OIDC Clients) - github.com
- did-siop - npm Package... - snyk.io
- DID-SIOP - Chrome Web Store - google.com
- SIOP-DID Tools - didsiop.org
DID-SIOP brings the authorization provider service under the control of true owner of the identity and its meta data. In other words: > DID-SIOP replace Social Login Schemes with a software module run out of his/her browser (as an add-on).
Significance of this is that, identification and personal data will be under the full control of the owner of the data and will prevent unauthorized use of such data by any other party.