From 68d8376bdb82972025dba39be06e43041d659825 Mon Sep 17 00:00:00 2001 From: Steve Behrendt Date: Fri, 7 Jul 2017 11:12:41 +0200 Subject: [PATCH] Update README.md fixed typo --- auth-server/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/auth-server/README.md b/auth-server/README.md index a1fccb4..38cb2e6 100644 --- a/auth-server/README.md +++ b/auth-server/README.md @@ -1,7 +1,7 @@ # Auth-Server ## Introduction -This service acts as the authetication and authorization service for the ecosystem of micro-services that we developed. Since each micro-service needs to authenticate the user, we provide a "/me" endpoint exposed by the auth-server that provides the logged in user. +This service acts as the authentication and authorization service for the ecosystem of micro-services that we developed. Since each micro-service needs to authenticate the user, we provide a "/me" endpoint exposed by the auth-server that provides the logged in user. This is ok for development/demo purposes but would lead to lots of chitchat since each micro-service needs to call the "/me" endpoint to authenticate the user. In typical production scenario, prefer to use a JWT (Json Web Token) wherein the token itself contains enough information for the resource server to do simple user authentication. The "/me" enpoint still needs to be used by the browser to see if the user is authenticated or not; but is not required in intra-service communication.