Microsoft bids to overhaul ID verification

Its agreat shame that Microsoft hasnt followed the SSI prinicples regarding its inplementation, if it had, then privacy would have been key. In addition, the centralised nature of AD also causes issues - but if its a way of using verifiable credentials and link them back to your more traditional AD approach - then that is a good thing...Its all dependent on the real world usecase.

I should have added, the issue of identitiy needs to be a cautionary one. We cannot afford to get "identity" infrastructure wrong, there is too much at stake.

Digital identity, cautionary facts – FinTechAndrew – The blog (wordpress.com)

The issue of identity managment is a very sensitive issue and I agree with Andrew Smith's comments above. Additionally, I may add that if there is no connectivity neither AD nor RTGS will work. The other issue is delay ( latency) and security, as the information flows it can be compromised as we move from server to server before it reaches you. To address, the above we invented next generation connectivity whereby RTGS happens even when no internet in a secure manner in real time . I think with further development a solution could be developed that unquestionably link a transaction to an individual (or organisations) uniformally and to systems in real time, ofcourse even when no internet.

@Rajan, we are working on just that ;)

privilage to collaborate ☼

As a lay person with some knowledge of the questions, one wonders how we will develop a model where each of my claims (read attributes) can be trusted by a myriad of parties.  My claims will include graduation from University, Birth, marriage(s), divorce(s), Vaccination(s), certificate(s) of complaince to a defined work capability, business permit(s), employment(s) and the list goes on.  Without agreement on the schema associated with the multiple claims I wish to have trusted, how all of this will work is open to discussion. 

One then thinks about the work of ISO on 80013, 8583, 20022, 781z, and ... then add ICAO on the electronic passport, AAMVA on the Mobile drivers license and all sorts of relationship, membership  andtransactions types like airline tickets, theater tickets, bus passes.

What am I missing I am sure the list is enormous.

In response to Philip A. - the list of digital identity use-cases is in fact endless. Over time next to all transactions will be digital even when happening f2f. The solution is to separate the transaction authorization with strong authentication based on verified identity from the transaction processing. This is already happening in e.g. payments with 3DS 2.0. With separation, the transaction processing complexity is an use-case & industry specific issue.