You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This change changes the Idemix MSP folder structure to match the
structure expected by Fabric. It replicates the changes previously
delivered (and subsequently reverted) in the following commits:
- acea746
- 29e083e
- 0fcf897
- dfd29fe
- 77c54da
Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>
Co-authored-by: Angelo De Caro <adc@zurich.ibm.com>
Copy file name to clipboardExpand all lines: docs/source/deployguide/cadeploy.md
+48-50Lines changed: 48 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,11 +39,10 @@ Because you will use a single CA client to submit register and enrollment reques
39
39
40
40
```
41
41
fabric-ca-client
42
-
├── int-ca
43
-
├── org1-ca
44
-
├── tls-ca
45
-
└── tls-root-cert
46
-
42
+
├── int-ca
43
+
├── org1-ca
44
+
├── tls-ca
45
+
└── tls-root-cert
47
46
```
48
47
49
48
**Important:** If your Fabric CA client will transact with CAs from multiple organizations that are secured by different TLS servers, then you would need to either create different `tls-root-cert` folders to hold the TLS CA root certificate for each organization or simply name them differently inside the folder to differentiate them. Since our Fabric CA client will only be transacting with CA servers in the same organization, all of which are secured by the same TLS CA, we will only have a single root certificate in this folder.
@@ -194,8 +193,8 @@ The folder structure that we are using for these Fabric CA client commands is:
194
193
195
194
```
196
195
fabric-ca-client
197
-
└── tls-ca
198
-
└── tls-root-cert
196
+
├── tls-ca
197
+
└── tls-root-cert
199
198
```
200
199
201
200
These folders are used by the Fabric CA client to:
@@ -293,15 +292,15 @@ The resulting folder structure resembles:
293
292
294
293
```
295
294
fabric-ca-client
296
-
└── tls-ca
297
-
└── tlsadmin
298
-
└── msp
299
-
└── rcaadmin
300
-
└── msp
301
-
└── icaadmin
302
-
└── msp
295
+
└── tls-ca
296
+
├── tlsadmin
297
+
| └── msp
298
+
├── rcaadmin
299
+
| └── msp
300
+
├── icaadmin
301
+
| └── msp
303
302
└── tls-root-cert
304
-
└── tls-ca-cert.pem
303
+
└── tls-ca-cert.pem
305
304
```
306
305
307
306
**Tip:** After you have registered all your nodes with the TLS CA, it can be safely turned off.
@@ -336,19 +335,19 @@ Because you've already registered and enrolled your organization CA bootstrap id
336
335
337
336
```
338
337
fabric-ca-client
339
-
└── tls-ca
340
-
├── rcaadmin
341
-
├── msp
342
-
├── IssuerPublicKey
343
-
├── IssuerRevocationPublicKey
344
-
├── cacerts
345
-
├── keystore
346
-
└── key.pem
347
-
├── signcerts
348
-
└── cert.pem
338
+
└── tls-ca
339
+
└── rcaadmin
340
+
└── msp
341
+
├── IssuerPublicKey
342
+
├── RevocationPublicKey
343
+
├── cacerts
344
+
├── keystore
345
+
| └── key.pem
346
+
└── signcerts
347
+
└── cert.pem
349
348
fabric-ca-server-org1
350
-
└── tls
351
-
└── cert.pem
349
+
└── tls
350
+
├── cert.pem
352
351
└── key.pem
353
352
```
354
353
@@ -401,7 +400,7 @@ The folder structure we are using for these commands is:
401
400
402
401
```
403
402
fabric-ca-client
404
-
└── org1-ca
403
+
├── org1-ca
405
404
└── tls-root-cert
406
405
```
407
406
@@ -443,14 +442,13 @@ These folders are used by the Fabric CA client to:
0 commit comments