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.
Tag Archives: authorisation
How smart is #Smart #Contract?
The first time I heard about the automation of contract negotiation and agreement in 2001-2002. It was written in ebXML (backed by OASIS and UN/CEFACT). It was an amazing achievement because the first SML Conference took place just in 2001. The endeavour fails because of two major reasons, as I learnt later: Recent splash of …
HOW to ARCHITECT for DEVELOPERS 