Summary of Distributed Matrix Management for Personal Digital Identity & Humanistic Social Model

A humanistic digital identity for a person is proposed. It is accompanied with a description of societal model that preserve an individual well-being and personal prosperity inder the “Reciprocal Liberty” principle.

Self-Sovereign Digital Identity: Humanistic AI against Digital Slavery

No needs for UDI or DIPP for Human Society. Digital identities like UDI or DIPP ignore human personality and lead to digital slavery. The personal Digital Identity based on the real-life facts about the person allow correct identification of a person among 8.4 billions of people and free from spying over person’s activities online, personal biomedical information and behavioural monitoring of the person.Definitions, parameters, examples and statistical confirmations are provided for your assessment.

On the AI Road that Leads to Identity Hell

A notion of personal identity and Identity Management (IM) are frequently mixed, creating a misreading and speculations about “which one leads the dance”. An appearance of AI has finally put some light on the purpose of this strange mixture. Now, I can say that without an AI-enabled digital identity, you are nobody.

#Microservice #Protection based on the principle of #Zero #Trust

The task addressed in the article is about protecting Microservice’s functionality and resources in the inter-Microservice interactions. Known techniques like OpenID Connects, JWT and OAuth2 were reviewed from the perspective of Microservice interactions. It has been found that these techniques cannot be applied as-is to the Microservices either because unanswered questions to them or because of doubtful trustfulness of related workflows.
The article proposes two protective methods for Microservice (or service) that have sensitive functionality and/or resources. While the Basic Protection Method is just a classic identity verification and following access permission control, the method does not require single centralised Identity and Permission Authorities. The latter can be distributed as needed following the distribution of Microservice-based applications. The Closed Optimised Protection Method replaces Identity and Permission Authorities with Dependency Catalogue Service per application and provides full protection with performance comparable with OpenID-JWT/OAuth2.