We've added self-sovereign ID to HIE of One using uPort. This now gives the resource owner 4 options for authentication at the UMA AS

1. Direct Login to the AS
   
2. Whitelisting OIDC IDPs as an option of UMA resource registration
3. Federated login using OIDC
4. Self-sovereign Blockchain ID with linked verifiable claims

These 4 options are demonstrated in the latest addition to HIE of One in a 2-minute video: https://youtu.be/FNlAkGauIdw

Your recent slides seem somewhat harsh on self-soveriegn ID. Sovrin is just one of the blockchain-based self-sovereign IDs that are currently being standardized. Let's review your concluding slide:

​

1. The uPort app doesn't require the user to remember either a username or password
2. I'm not sure how to interpret "unilateral user actions" - please elaborate
3. People have rejected federation for anything other than low levels of assurance. A self-sovereign ID can be high assurance while also protecting pseudonimity through separable verifiable claims.
   
4. Self-sovereign ID respects the needs of RS (strong authentication), AS (open reputation mechanism and verifiable claims, and RqP (triple-blind attribute handling, privacy-preserving claims, on ID app across all domains).
5. I'm not sure how to interpret "consent more meaningful in this context" - please elaborate
6. The limits of federation are now obvious. Standards-based self-sovereign ID seems much more likely to scale.

Adrian