From bbfd856433771c9bec50f7735611633fd82617f3 Mon Sep 17 00:00:00 2001
From: "kanta.sasaki" <49396455+atomic-kanta-sasaki@users.noreply.github.com>
Date: Mon, 1 Jul 2024 17:05:19 +0900
Subject: [PATCH] Update cadeploy.md

fix:  command registers the organization CA bootstrap identity rcaadmin with password rcaadminpw with the TLS CA.

Signed-off-by: kanta.sasaki <49396455+atomic-kanta-sasaki@users.noreply.github.com>
---
 docs/source/deployguide/cadeploy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/source/deployguide/cadeploy.md b/docs/source/deployguide/cadeploy.md
index 939ade925..ae553c910 100644
--- a/docs/source/deployguide/cadeploy.md
+++ b/docs/source/deployguide/cadeploy.md
@@ -230,7 +230,7 @@ The following diagram is a conceptual summary of the steps you perform to create
 The TLS CA server was started with a bootstrap admin identity (tlsadmin) which has full admin privileges for the server. One of the key abilities of the admin is the ability to register new identities. Each node in the organization (orderers, peers, organization CAs) that will transact on the network needs to be registered with the TLS CA, so that each node can then enroll to get their TLS certificate. Therefore, before we set up the organization CA, we need to use the TLS CA to register and enroll the organization CA bootstrap identity to get its TLS certificate and private key. The organization CA bootstrap admin user will be named `rcaadmin` in the next step, therefore we will generate the TLS identity for the organization CA using the same name. The following command registers the organization CA bootstrap identity `rcaadmin` with password `rcaadminpw` with the TLS CA.
 
 ```
-./fabric-ca-client register -d --id.name rcaadmin --id.secret rcaadminpw -u https://my-machine.example.com:7054  --tls.certfiles tls-root-cert/tls-ca-cert.pem --mspdir tls-ca/tlsadmin/msp
+./fabric-ca-client register -d --id.name rcaadmin --id.secret rcaadminpw -u https://tls-admin:tls-adminpw@my-machine.example.com:7054  --tls.certfiles tls-root-cert/tls-ca-cert.pem --mspdir tls-ca/tlsadmin/msp
 ```
 
 Notice that the `--mspdir` flag on the command points to the location of TLS CA admin msp certificates that we generated in the previous step. This crypto material is required to be able to register nodes with the TLS CA.