From a3d1fb399c16f00a3b5ebf4e99b7f75e6567917e Mon Sep 17 00:00:00 2001
From: juliusvonkohout <45896133+juliusvonkohout@users.noreply.github.com>
Date: Wed, 13 Nov 2024 14:53:23 +0100
Subject: [PATCH] add Dex, oauth2 and k8s token guidance

Signed-off-by: juliusvonkohout <45896133+juliusvonkohout@users.noreply.github.com>
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 5e36878c4..541bb6ac5 100644
--- a/README.md
+++ b/README.md
@@ -277,7 +277,7 @@ kustomize build common/dex/overlays/oauth2-proxy | kubectl apply -f -
 kubectl wait --for=condition=ready pods --all --timeout=180s -n auth
 ```
 
-To connect to your desired identity providers (LDAP,GitHub,Google,Microsoft,Bitbucket Cloud,LinkedIn,OIDC,SAML,GitLab) please take a look at https://dexidp.io/docs/connectors/oidc/.
+To connect to your desired identity providers (LDAP,GitHub,Google,Microsoft,OIDC,SAML,GitLab) please take a look at https://dexidp.io/docs/connectors/oidc/.
 We recommend to use OIDC in general, since it is compatible with most providers as for example azure in the following example.
 You need to modify https://github.com/kubeflow/manifests/blob/master/common/dex/overlays/oauth2-proxy/config-map.yaml and add some environment variables in https://github.com/kubeflow/manifests/blob/master/common/dex/base/deployment.yaml by adding a patch section in your main Kustomization file. For guidance please check out [Upgrading and extending](#upgrading-and-extending).
 
@@ -569,7 +569,7 @@ For security reasons, we don't want to use the default username and email for th
 
 ### Change default user password
 
-If you have an identy provider (LDAP,GitHub,Google,Microsoft,Bitbucket Cloud,LinkedIn,OIDC,SAML,GitLab) available you should use that instead of static passwords and connect it to oauth2-proxy or Dex as explained in the sections above. This is best practices instead of using static passwords. 
+If you have an identy provider (LDAP,GitHub,Google,Microsoft,OIDC,SAML,GitLab) available you should use that instead of static passwords and connect it to oauth2-proxy or Dex as explained in the sections above. This is best practices instead of using static passwords. 
 
 For security reasons, we don't want to use the default static password for the default Kubeflow user when installing in security-sensitive environments. Instead, you should define your own password and apply it either **before creating the cluster** or **after creating the cluster**.