1. Digital ID and Authentication as a Platform Peter Watkins

2. Canonical Use Cases Digital ID and Authentication Ecosystem The beer store The medical lab results The bank account

3. Canonical Use Cases Digital ID and Authentication Ecosystem The beer store The medical lab results The bank account

4. Step 0

5. Step 1

6. Touch “New Customer” Step 2

7. Be advised about what info they need, why, what they will do with it etc.. Step 3

8. Passcode and/or Card Tap etc. Authentication Step 4

9. Authentication and authorization agent shows you the request and asks you to proceed… Step 5

10. Full activation may take 24-48hrs; meanwhile… Step Done!

11. Considerations Key Actors Applicant (user) Bank app from the app store Government entity trusted for name, dob, address Agent (for the user) that ran on the phone

12. Considerations Not Shown Technical architecture, technical specifications, protocols Phone registration / agent activation Credential used during phone registration Credential issuance / activation User’s registration with government entity that provided name, dob, address Bank app development/developer/registration Agent accreditation/certification Privacy enabling infrastructure/services Assurance standards Evidence of identity standards …

13. Plan to see session by Dick Hardt on Authentication and Authorization Privacy Protecting Protocol A2P3 Tomorrow

14. Segue… Even with answers to all the previous items How was it that the bank was able to meet its obligations per: KYC/AML etc. through this approach?

15. What else?

16. Barriers to Collective Success (some of the things we have to talk about, or ignore at our peril) Ensuring Privacy By Design Liability Rules Reputation Risk Ubiquity Of Platform Access, Interoperability Equality Of Service Irrespective Of Technology Access, (Dis)ability, Age, Etc. What Will The Trust Frameworks Be? Compelling Use Cases Responsibility to Educate Consumers Enabling Consumer Power – Vs. Relying Party Power – Vs. Identity Provider Power