Inspiration
Governments around the globe issues may hundred of different identity document throughout our lifetime. From passports, to driving licences to professional credentials and criminal records.
These identities are dispersed in the thousands of locations each has their weak vulnerabilities and attach surfaces. As a result, in the UK, 189,108 reported cases of identity fraud in 2018 alone and Identity theft in the UK accounts for 53% of online fraud.
What it does
Gov OneID streamline Citizens Identity Issuance process while give them full control over how and whn they share them.
How we built it
The MVP will be using the following:
- AAD VC: Issue and Verification of DID Claims
- Azure Integration Services(APIM, Logic App and Functions): This does the heavy lifting: 1) create/update/delate rule files. 2) Integrate with Gov downstream system of record based on particular events(i.e. driving points/ban) 3) API Gateway to stream line both downstream integration and upstream VC verifications.
- Azure Storage Immutable Storage: Store Rules, DIDs and prevents accidental edits/updates (Ideally Confidential Ledger, but it is limited with AAD VC integration)
Challenges we ran into
- Integration with AAD VC Issuance APIs and how to dynamically change claims
- It highly advisable that Confidential nodes will be used to climate Cloud provider trust
What's next for Gov OneID
MVP Implementation phase with presentation to Gov Customers.
Built With
- aad
- azureapim
- azurefunctions
- c#
- did
- logicapp
Log in or sign up for Devpost to join the conversation.