From bb670753dca260b9ca462141d8d3d3af3c185533 Mon Sep 17 00:00:00 2001 From: ptyagii Date: Wed, 7 May 2025 11:42:15 -0700 Subject: [PATCH] corrected the hyperlink for component certs --- migration/nonRBACToRBAC/mtlsLdap/README.md | 2 +- migration/nonRBACToRBAC/mtlsOAuth/README.md | 2 +- migration/nonRBACToRBAC/mtlsOnly/README.md | 3 +-- security/mds-mtls-c3-sso/README.md | 2 +- security/mds-mtls-with-vault/README.md | 2 +- security/mtls-rbac-with-sso-oauth/README.md | 2 +- 6 files changed, 6 insertions(+), 7 deletions(-) diff --git a/migration/nonRBACToRBAC/mtlsLdap/README.md b/migration/nonRBACToRBAC/mtlsLdap/README.md index b1254d78..9e946e45 100644 --- a/migration/nonRBACToRBAC/mtlsLdap/README.md +++ b/migration/nonRBACToRBAC/mtlsLdap/README.md @@ -65,7 +65,7 @@ exit In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name. Each Confluent component service should have its own TLS certificate. In this scenario, you'll -generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates. +generate a server certificate for each Confluent component service. Follow [these instructions](../../../assets/certs/component-certs/README.md) to generate these certificates. ## Deploy configuration secrets diff --git a/migration/nonRBACToRBAC/mtlsOAuth/README.md b/migration/nonRBACToRBAC/mtlsOAuth/README.md index 7e6a08de..9dd3e14a 100644 --- a/migration/nonRBACToRBAC/mtlsOAuth/README.md +++ b/migration/nonRBACToRBAC/mtlsOAuth/README.md @@ -46,7 +46,7 @@ kubectl get pods -n confluent In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name. Each Confluent component service should have its own TLS certificate. In this scenario, you'll -generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates. +generate a server certificate for each Confluent component service. Follow [these instructions](../../../assets/certs/component-certs/README.md) to generate these certificates. ## Deploy configuration secrets diff --git a/migration/nonRBACToRBAC/mtlsOnly/README.md b/migration/nonRBACToRBAC/mtlsOnly/README.md index 32259c4e..e19caed2 100644 --- a/migration/nonRBACToRBAC/mtlsOnly/README.md +++ b/migration/nonRBACToRBAC/mtlsOnly/README.md @@ -34,11 +34,10 @@ kubectl get pods -n confluent In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name. Each Confluent component service should have its own TLS certificate. In this scenario, you'll -generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates. +generate a server certificate for each Confluent component service. Follow [these instructions](../../../assets/certs/component-certs/README.md) to generate these certificates. ## Deploy configuration secrets - You'll use Kubernetes secrets to provide credential configurations. With Kubernetes secrets, credential management (defining, configuring, updating) diff --git a/security/mds-mtls-c3-sso/README.md b/security/mds-mtls-c3-sso/README.md index a1c9fd47..d6925ad8 100644 --- a/security/mds-mtls-c3-sso/README.md +++ b/security/mds-mtls-c3-sso/README.md @@ -53,7 +53,7 @@ kubectl get pods -n confluent In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name. Each Confluent component service should have its own TLS certificate. In this scenario, you'll -generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates. +generate a server certificate for each Confluent component service. Follow [these instructions](../../assets/certs/component-certs/README.md) to generate these certificates. ## Deploy configuration secrets diff --git a/security/mds-mtls-with-vault/README.md b/security/mds-mtls-with-vault/README.md index 3a957946..329efc6c 100644 --- a/security/mds-mtls-with-vault/README.md +++ b/security/mds-mtls-with-vault/README.md @@ -161,7 +161,7 @@ cat /tmp/fileUserPassword.txt | base64 | vault kv put /secret/fileuser.txt fileu In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name. Each Confluent component service should have its own TLS certificate. In this scenario, you'll -generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates. +generate a server certificate for each Confluent component service. Follow [these instructions](../../assets/certs/component-certs/README.md) to generate these certificates. ## Deploy configuration secrets diff --git a/security/mtls-rbac-with-sso-oauth/README.md b/security/mtls-rbac-with-sso-oauth/README.md index df796fd3..780409e3 100644 --- a/security/mtls-rbac-with-sso-oauth/README.md +++ b/security/mtls-rbac-with-sso-oauth/README.md @@ -53,7 +53,7 @@ kubectl get pods -n confluent In this scenario, you'll configure internal authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name. Each Confluent component service should have its own TLS certificate. In this scenario, you'll -generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates. +generate a server certificate for each Confluent component service. Follow [these instructions](../../assets/certs/component-certs/README.md) to generate these certificates. ## Deploy configuration secrets