diff --git a/content/v1.2.x/deployment/security/keycloak/bare-metal.md b/content/v1.2.x/deployment/security/keycloak/bare-metal.md
index d6a11119c..b5accd357 100644
--- a/content/v1.2.x/deployment/security/keycloak/bare-metal.md
+++ b/content/v1.2.x/deployment/security/keycloak/bare-metal.md
@@ -7,7 +7,7 @@ slug: /deployment/security/keycloak/bare-metal
 
 ## Update conf/openmetadata.yaml
 
-Once the `Client Id` and `Client Secret` are generated add the `Client Id` in `openmetadata.yaml` file in `client_id` field.
+Once the `Client Id` is generated add the `Client Id` in `openmetadata.yaml` file in `client_id` field.
 
 Update the `providerName` config to the name you want to display in the `Sign In` button in the UI. For example, with the
 following configuration with `providerName` set to `KeyCloak`, the users will see `Sign In with KeyCloak SSO` in the `Sign In`
diff --git a/content/v1.2.x/deployment/security/keycloak/kubernetes.md b/content/v1.2.x/deployment/security/keycloak/kubernetes.md
index 3768d6213..fb8189ff7 100644
--- a/content/v1.2.x/deployment/security/keycloak/kubernetes.md
+++ b/content/v1.2.x/deployment/security/keycloak/kubernetes.md
@@ -7,14 +7,9 @@ slug: /deployment/security/keycloak/kubernetes
 
 Check the Helm information [here](https://artifacthub.io/packages/search?repo=open-metadata).
 
-Once the `Client Id` and `Client Secret` are generated, see the snippet below for an example of where to
+Once the `Client Id` is generated, see the snippet below for an example of where to
 place the client id value and update the authorizer configurations in the `values.yaml`.
 
-Create a secret in kubernetes with the client secret:
-```shell
-kubectl create secret generic custom-oidc-key-secret --namespace=dev-open-metadata --from-literal=custom-oidc-key-secret=<change-for-your-secret>
-```
-
 The configuration below already uses the presets shown in the example of keycloak configurations, you can change to yours.
 
 ```yaml