From dbfb9078430e2fbe381ae687a51fc3e051835c7b Mon Sep 17 00:00:00 2001 From: Parham Alvani Date: Sat, 21 Oct 2023 03:13:02 +0000 Subject: [PATCH] feat: update readme --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9330a29..4c311e8 100644 --- a/README.md +++ b/README.md @@ -12,9 +12,9 @@ ## Introduction -Soteria is responsible for Authentication and Authorization of every request sent to EMQ. +Soteria is responsible for Authentication and Authorization of every request sent to [EMQ](https://github.com/emqx/emqx/). The following configuration in [HOCON](https://github.com/lightbend/config/blob/master/HOCON.md) -format, configure EMQX to use HTTP Service for Authentication and Authorization. +format, configure EMQ to use HTTP Service for Authentication and Authorization. ```hocon { @@ -60,7 +60,7 @@ format, configure EMQX to use HTTP Service for Authentication and Authorization. We are using the [Authentication HTTP Service](https://www.emqx.io/docs/en/v5.2/access-control/authn/http.html) and [Authorization HTTP Service](https://www.emqx.io/docs/en/v5.2/access-control/authn/http.html) plugins of EMQ for forwarding these requests to Soteria and doing Authentication and Authorization. -EMQX has caching mechanism, but it sends requests almost for each Publish message to Soteria. +EMQ has caching mechanism, but it sends requests almost for each Publish message to Soteria. PS: On Subscribe we have only one message from client that need authorization and other messages are coming from server. ## Deployment