From 07020f5ef05d2f180da57d4abbe9211a97cdb10d Mon Sep 17 00:00:00 2001 From: boneyard93501 Date: Tue, 13 Apr 2021 13:55:56 +0000 Subject: [PATCH] GitBook: [docs] one page modified --- knowledge_knowledge/knowledge_security.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/knowledge_knowledge/knowledge_security.md b/knowledge_knowledge/knowledge_security.md index 43cf65d..eff9b90 100644 --- a/knowledge_knowledge/knowledge_security.md +++ b/knowledge_knowledge/knowledge_security.md @@ -6,8 +6,6 @@ In the Fluence network, an application consists of one or more services composed Aquamarine, as a composability medium, needs to take care of many aspects of security to enable composing services of different vendors in a safe way. Let's consider the example of authorization service – a service that verifies permission: -\`\`\`{scala, tidy=FALSE, eval=FALSE, highlight=FALSE } // Pseudocode of a service interface service Auth: // Works only for the service creator def grant\_permission\(to\_peer: PeerId\) def check\_permission\(\): bool - ```text // Pseudocode of a service interface service Auth: