From 9a101e1ed04bd57df802421dcd5247e764b9ba55 Mon Sep 17 00:00:00 2001 From: Shane Myrick Date: Tue, 5 Mar 2024 10:42:53 -0800 Subject: [PATCH] [docs] Update authentication docs with link to Router (#7826) Add links to Router docs for those who may land on the page from external or internal direct links --- docs/source/security/authentication.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/source/security/authentication.mdx b/docs/source/security/authentication.mdx index 7b87727d034..0f423650ac9 100644 --- a/docs/source/security/authentication.mdx +++ b/docs/source/security/authentication.mdx @@ -10,6 +10,14 @@ Your GraphQL API probably needs to control which users can see and interact with - **Authentication** is determining whether a given user is logged in, and subsequently determining _which_ user someone is. - **Authorization** is then determining what a given user has permission to do or see. + + +Apollo Router can now provide authentication and authorization for your entire supergraph. While it may make sense to re-apply auth checks at a subgraph level or in a monolith graph, the Apollo Router has built and provided standard JWT checks that can be setup with a simple YAML configuration and enforce this in a central location for all subgraphs: + +https://www.apollographql.com/blog/centrally-enforce-policy-as-code-for-graphql-apis + + + ## Putting authenticated user info in your `contextValue`