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
Replace all references to 'user' with 'identity' in the doc
Also, updated fabric-ca-server and fabric-ca-client command
help, removed yml comments that said certfiles property is
comma separated values.
Change-Id: I2d399634080a1533b77af596b4296c6dbd856911
Signed-off-by: Anil Ambati <aambati@us.ibm.com>
--csr.cn string The common name field of the certificate signing request to a parent fabric-ca-server
208
-
--csr.serialnumber string The serial number in a certificate signing request to a parent fabric-ca-server
212
+
--csr.cn string The common name field of the certificate signing request
213
+
--csr.hosts stringSlice A list of space-separated host names in a certificate signing request
214
+
--csr.serialnumber string The serial number in a certificate signing request
209
215
-d, --debug Enable debug level logging
210
216
--enrollment.hosts string Comma-separated host list
211
217
--enrollment.label string Label to use in HSM operations
@@ -218,14 +224,14 @@ The following shows the Fabric CA client usage message:
218
224
--id.type string Type of identity being registered (e.g. 'peer, app, user')
219
225
-M, --mspdir string Membership Service Provider directory (default "msp")
220
226
-m, --myhost string Hostname to include in the certificate signing request during enrollment (default "$HOSTNAME")
221
-
--tls.certfiles stringPEM-encoded comma separated list of trusted certificate files (e.g. root1.pem, root2.pem)
222
-
--tls.client.certfile string PEM-encoded certificate file when mutual authentication is enabled
227
+
--tls.certfiles stringSlice PEM-encoded list of trusted certificate files
228
+
--tls.client.certfile string PEM-encoded certificate file when mutual authenticate is enabled
223
229
--tls.client.keyfile string PEM-encoded key file when mutual authentication is enabled
224
-
--tls.enabled Enable TLS for client connection
225
-
-u, --url string URL of fabric-ca-server (default "http://localhost:7054")
230
+
-u, --url string URL of the Fabric CA server (default "http://localhost:7054")
226
231
227
232
Use "fabric-ca-client [command] --help" for more information about a command.
228
233
234
+
Note that command line options that are string slices (lists) can be specified either by specifying the option with space-separated list elements or by specifying the option multiple times, each with a string value that make up the list. For example, to specify ``host1`` and ``host2`` for `csr.hosts` option, you can either pass `--csr.hosts "host1 host2"` or `--csr.hosts host1 --csr.hosts host2`
229
235
230
236
`Back to Top`_
231
237
@@ -270,25 +276,25 @@ the server's home directory (see `Fabric CA Server <#server>`__ section more inf
@@ -526,7 +534,8 @@ directory, ``cert.pem`` file in the ``~/config/certs`` directory and the
526
534
527
535
tls:
528
536
enabled: true
529
-
certfiles: root.pem
537
+
certfiles:
538
+
- root.pem
530
539
client:
531
540
certfile: certs/cert.pem
532
541
keyfile: /abs/path/key.pem
@@ -538,11 +547,9 @@ Fabric CA Server
538
547
539
548
This section describes the Fabric CA server.
540
549
541
-
You may initialize the Fabric CA server before starting it if you prefer.
542
-
This provides an opportunity for you to generate a default configuration
543
-
file but to review and customize its settings before starting it.
550
+
You may initialize the Fabric CA server before starting it. This provides an opportunity for you to generate a default configuration file but to review and customize its settings before starting it.
544
551
545
-
|The fabric-ca-server's home directory is determined as follows:
552
+
|The Fabric CA server's home directory is determined as follows:
546
553
|- if the ``FABRIC_CA_SERVER_HOME`` environment variable is set, use
547
554
its value;
548
555
|- otherwise, if ``FABRIC_CA_HOME`` environment variable is set, use
@@ -569,14 +576,14 @@ Initialize the Fabric CA server as follows:
569
576
570
577
# fabric-ca-server init -b admin:adminpw
571
578
572
-
The ``-b`` (bootstrap user) option is required for initialization. At
573
-
least one bootstrap user is required to start the fabric-ca-server. The
579
+
The ``-b`` (bootstrap identity) option is required for initialization. At
580
+
least one bootstrap identity is required to start the Fabric CA server. The
574
581
server configuration file contains a Certificate Signing Request (CSR)
575
582
section that can be configured. The following is a sample CSR.
576
583
577
-
If you are going to connect to the fabric-ca-server remotely over TLS,
584
+
If you are going to connect to the Fabric CA server remotely over TLS,
578
585
replace "localhost" in the CSR section below with the hostname where you
579
-
will be running your fabric-ca-server.
586
+
will be running your Fabric CA server.
580
587
581
588
.. _csr-fields:
582
589
@@ -614,7 +621,7 @@ command again.
614
621
The ``fabric-ca-server init`` command generates a self-signed CA certificate
615
622
unless the ``-u <parent-fabric-ca-server-URL>`` option is specified.
616
623
If the ``-u`` is specified, the server's CA certificate is signed by the
617
-
parent fabric-ca-server. The ``fabric-ca-server init`` command also
624
+
parent Fabric CA server. The ``fabric-ca-server init`` command also
618
625
generates a default configuration file named **fabric-ca-server-config.yaml**
619
626
in the server's home directory.
620
627
@@ -671,10 +678,10 @@ server will generate the ca-cert.pem and ca-key.pem files if they don't
671
678
yet exist and will also create a default configuration file if it does
672
679
not exist. See the `Initialize the Fabric CA server <#initialize>`__ section.
673
680
674
-
Unless the fabric-ca-server is configured to use LDAP, it must be
675
-
configured with at least one pre-registered bootstrap user to enable you
681
+
Unless the Fabric CA server is configured to use LDAP, it must be
682
+
configured with at least one pre-registered bootstrap identity to enable you
676
683
to register and enroll other identities. The ``-b`` option specifies the
677
-
name and password for a bootstrap user.
684
+
name and password for a bootstrap identity.
678
685
679
686
A different configuration file may be specified with the ``-c`` option
To cause the fabric-ca-server to listen on ``https`` rather than
693
+
To cause the Fabric CA server to listen on ``https`` rather than
687
694
``http``, set ``tls.enabled`` to ``true``.
688
695
689
696
To limit the number of times that the same secret (or password) can be
690
697
used for enrollment, set the ``registry.maxEnrollments`` in the configuration
691
-
file to the appropriate value. If you set the value to 1, the fabric-ca
698
+
file to the appropriate value. If you set the value to 1, the Fabric CA
692
699
server allows passwords to only be used once for a particular enrollment
693
-
ID. If you set the value to 0, the fabric-ca-server places no limit on
700
+
ID. If you set the value to 0, the Fabric CA server places no limit on
694
701
the number of times that a secret can be reused for enrollment. The
695
702
default value is 0.
696
703
697
-
The fabric-ca-server should now be listening on port 7054.
704
+
The Fabric CA server should now be listening on port 7054.
698
705
699
706
You may skip to the `Fabric CA Client <#fabric-ca-client>`__ section if
700
-
you do not want to configure the fabric-ca-server to run in a cluster or
707
+
you do not want to configure the Fabric CA server to run in a cluster or
701
708
to use LDAP.
702
709
703
710
Configuring the database
704
711
~~~~~~~~~~~~~~~~~~~~~~~~
705
712
706
-
This section describes how to configure the fabric-ca-server to connect
713
+
This section describes how to configure the Fabric CA server to connect
707
714
to Postgres or MySQL databases. The default database is SQLite and the
708
715
default database file is ``fabric-ca-server.db`` in the Fabric CA
709
716
server's home directory.
710
717
711
-
If you don't care about running the fabric-ca-server in a cluster, you
718
+
If you don't care about running the Fabric CA server in a cluster, you
712
719
may skip this section; otherwise, you must configure either Postgres or
713
720
MySQL as described below.
714
721
@@ -758,15 +765,15 @@ values for sslmode are:
758
765
|| signed by a |
759
766
|| trusted CA and |
760
767
|| the server |
761
-
||host name|
768
+
||hostname|
762
769
|| matches the |
763
770
|| one in the |
764
771
|| certificate |
765
772
+----------------+----------------+
766
773
767
774
|
768
775
769
-
If you would like to use TLS, then the ``db.tls`` section in the fabric-ca-server
776
+
If you would like to use TLS, then the ``db.tls`` section in the Fabric CA server
770
777
configuration file must be specified. If SSL client authentication is enabled
771
778
on the Postgres server, then the client certificate and key file must also be
772
779
specified in the ``db.tls.client`` section. The following is an example
@@ -778,18 +785,19 @@ of the ``db.tls`` section:
778
785
...
779
786
tls:
780
787
enabled: true
781
-
certfiles: db-server-cert.pem
788
+
certfiles:
789
+
- db-server-cert.pem
782
790
client:
783
791
certfile: db-client-cert.pem
784
792
keyfile: db-client-key.pem
785
793
786
-
|**certfiles** - Comma separated list of PEM-encoded trusted root certificate files.
794
+
|**certfiles** - A list of PEM-encoded trusted root certificate files.
787
795
|**certfile** and **keyfile** - PEM-encoded certificate and key files that are used by the Fabric CA server to communicate securely with the Postgres server
788
796
789
797
MySQL
790
798
^^^^^^^
791
799
792
-
The following sample may be added to the fabric-ca-server config file in
800
+
The following sample may be added to the Fabric CA server configuration file in
793
801
order to connect to a MySQL database. Be sure to customize the various
794
802
values appropriately.
795
803
@@ -805,16 +813,16 @@ section is also required as described in the **Postgres** section above.
805
813
Configuring LDAP
806
814
~~~~~~~~~~~~~~~~
807
815
808
-
The fabric-ca-server can be configured to read from an LDAP server.
816
+
The Fabric CA server can be configured to read from an LDAP server.
809
817
810
-
In particular, the fabric-ca-server may connect to an LDAP server to do
818
+
In particular, the Fabric CA server may connect to an LDAP server to do
811
819
the following:
812
820
813
-
- authenticate a user prior to enrollment
814
-
- retrieve a user's attribute values which are used for authorization.
821
+
- authenticate an identity prior to enrollment
822
+
- retrieve an identity's attribute values which are used for authorization.
815
823
816
-
Modify the LDAP section of the server's configuration file to configure the
817
-
fabric-ca-server to connect to an LDAP server.
824
+
Modify the LDAP section of the Fabric CA server's configuration file to configure the
825
+
server to connect to an LDAP server.
818
826
819
827
::
820
828
@@ -858,21 +866,21 @@ server.
858
866
When LDAP is configured, enrollment works as follows:
859
867
860
868
861
-
- The fabric-ca-client or client SDK sends an enrollment request with a
869
+
- The Fabric CA client or client SDK sends an enrollment request with a
862
870
basic authorization header.
863
-
- The fabric-ca-server receives the enrollment request, decodes the
864
-
user name and password in the authorization header, looks up the DN (Distinquished
865
-
Name) associated with the user name using the "userfilter" from the
866
-
configuration file, and then attempts an LDAP bind with the user's
871
+
- The Fabric CA server receives the enrollment request, decodes the
872
+
identity name and password in the authorization header, looks up the DN (Distinquished
873
+
Name) associated with the identity name using the "userfilter" from the
874
+
configuration file, and then attempts an LDAP bind with the identity's
867
875
password. If the LDAP bind is successful, the enrollment processing is
868
876
authorized and can proceed.
869
877
870
878
When LDAP is configured, attribute retrieval works as follows:
871
879
872
880
873
881
- A client SDK sends a request for a batch of tcerts **with one or more
874
-
attributes** to the fabric-ca-server.
875
-
- The fabric-ca-server receives the tcert request and does as follows:
882
+
attributes** to the Fabric CA server.
883
+
- The Fabric CA server receives the tcert request and does as follows:
876
884
877
885
- extracts the enrollment ID from the token in the authorization
878
886
header (after validating the token);
@@ -883,10 +891,10 @@ When LDAP is configured, attribute retrieval works as follows:
883
891
Setting up a cluster
884
892
~~~~~~~~~~~~~~~~~~~~
885
893
886
-
You may use any IP sprayer to load balance to a cluster of fabric-ca
894
+
You may use any IP sprayer to load balance to a cluster of Fabric CA
887
895
servers. This section provides an example of how to set up Haproxy to
888
-
route to a fabric-ca-server cluster. Be sure to change hostname and port
889
-
to reflect the settings of your fabric-ca servers.
896
+
route to a Fabric CA server cluster. Be sure to change hostname and port
897
+
to reflect the settings of your Fabric CA servers.
890
898
891
899
haproxy.conf
892
900
@@ -911,7 +919,7 @@ haproxy.conf
911
919
server server3 hostname3:port
912
920
913
921
914
-
Node: If using TLS, need to use ``mode tcp``.
922
+
Note: If using TLS, need to use ``mode tcp``.
915
923
916
924
`Back to Top`_
917
925
@@ -922,7 +930,7 @@ Fabric CA Client
922
930
923
931
This section describes how to use the fabric-ca-client command.
924
932
925
-
|The fabric-ca-client's home directory is determined as follows:
933
+
|The Fabric CA client's home directory is determined as follows:
926
934
|- if the ``FABRIC_CA_CLIENT_HOME`` environment variable is set, use
927
935
its value;
928
936
|- otherwise, if the ``FABRIC_CA_HOME`` environment variable is set,
@@ -935,12 +943,12 @@ This section describes how to use the fabric-ca-client command.
935
943
The instructions below assume that the client configuration file exists
936
944
in the client's home directory.
937
945
938
-
Enrolling the bootstrap user
939
-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
946
+
Enrolling the bootstrap identity
947
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
940
948
941
949
First, if needed, customize the CSR (Certificate Signing Request) section
942
950
in the client configuration file. Note that ``csr.cn`` field must be set
943
-
to the ID of the bootstrap user. Default CSR values are shown below:
951
+
to the ID of the bootstrap identity. Default CSR values are shown below:
944
952
945
953
::
946
954
@@ -964,41 +972,40 @@ to the ID of the bootstrap user. Default CSR values are shown below:
964
972
965
973
See `CSR fields <#csr-fields>`__ for description of the fields.
966
974
967
-
Then run ``fabric-ca-client enroll`` command to enroll the user. For example,
968
-
following command enrolls an user whose ID is **admin** and password is **adminpw**
969
-
by calling fabric-ca-server that is running locally at 7054 port.
975
+
Then run ``fabric-ca-client enroll`` command to enroll the identity. For example,
976
+
following command enrolls an identity whose ID is **admin** and password is **adminpw**
977
+
by calling Fabric CA server that is running locally at 7054 port.
0 commit comments