From f6710aba91a5fa02ce2a84712beb8273ebc53f88 Mon Sep 17 00:00:00 2001 From: Patrik Oldsberg Date: Wed, 10 Apr 2024 11:24:28 +0200 Subject: [PATCH] Apply suggestions from code review Signed-off-by: Patrik Oldsberg --- beps/0007-auth-external-services/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/beps/0007-auth-external-services/README.md b/beps/0007-auth-external-services/README.md index 0bfd3074c5..6e0e3cabb4 100644 --- a/beps/0007-auth-external-services/README.md +++ b/beps/0007-auth-external-services/README.md @@ -140,6 +140,6 @@ Alternatively, we could maintain the current state by allowing callers to indepe Another alternative is to retain access control on a per-plugin basis, as demonstrated in https://github.com/backstage/backstage/pull/23441. Given the repetitive nature of this use-case, establishing a common mechanism may present a more favorable option. -### Shared Token Requestor +### Shared Token Requester -Implementing a shared token requestor, as showcased in https://github.com/backstage/backstage/pull/23465, offers another potential solution. This approach may streamline token management and enhance accessibility, but requires thorough consideration of its implications and integration into the existing system. +Implementing a shared token requester, as showcased in https://github.com/backstage/backstage/pull/23465, offers another potential solution. This approach may streamline token management and enhance accessibility, but requires thorough consideration of its implications and integration into the existing system.