From a4b2b5afe14230ea09be226774f06285181d0d62 Mon Sep 17 00:00:00 2001 From: Ayush Date: Mon, 18 Oct 2021 22:48:02 +0530 Subject: [PATCH] Avoid confusion by replacing "another service" with "dex" --- content/docs/using-dex.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/using-dex.md b/content/docs/using-dex.md index 8fade09..67d7680 100644 --- a/content/docs/using-dex.md +++ b/content/docs/using-dex.md @@ -17,7 +17,7 @@ Once you have dex up and running, the next step is to write applications that us The first category of apps are standard OAuth2 clients. Users show up at a website, and the application wants to authenticate those end users by pulling claims out of the ID token. -The second category of apps consume ID tokens as credentials. This lets another service handle OAuth2 flows, then use the ID token retrieved from dex to act on the end user's behalf with the app. An example of an app that falls into this category is the [Kubernetes API server][api-server]. +The second category of apps consume ID tokens as credentials. This lets dex handle OAuth2 flows, then use the ID token retrieved from dex to act on the end user's behalf with the app. An example of an app that falls into this category is the [Kubernetes API server][api-server]. ## Requesting an ID token from dex