paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 16 Packages Projects Releases Wiki Activity

Update docs/features/kubernetes/authstrategies.md

Browse Source 
Co-authored-by: Jamie Klassen <jamie.klassen@broadcom.com>
Signed-off-by: Andrés Mauricio Gómez P <andmagom@outlook.com>
This commit is contained in:
Andrés Mauricio Gómez P
2024-02-21 17:29:29 -05:00
committed by blam
parent e293e41ad5
commit a27d7d3bd5
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/kubernetes/authstrategies.md
+3 -3
View File
@@ -20,9 +20,9 @@ kubernetes clusters, it includes:
- `Client Side Providers` like `aks` or `oidc` where the user is authenticated with the cluster, getting only the
kubernetes permissions granted to that specific user.
Although there are `Server Side Providers` and `Client Side Providers`, an auth provider requires to have code on both sides, perhaps one of them doing
most of the authentication job, but notice that not all steps to authenticate against a Kubernetes Cluster are always executed exclusively on the server side or client side.
A Kubernetes authentication flow could require to split the authentication process among steps on the client side **and** steps on the server side.
Although there are `Server Side Providers` and `Client Side Providers`, authenticating with a cluster requires code on both sides. Perhaps one of them does
most of the job, but in general not all steps to authenticate against a Kubernetes cluster are always executed exclusively on the server side or client side.
A Kubernetes authentication flow could require splitting the authentication process among steps on the client side **and** steps on the server side.
## AuthenticationStrategy interface