Reading fabric-ca docs its not clear what is the purpose of fabric-ca-client register when it seems that fabric-ca-client enroll can be used to accomplish everything in the realm of fabric-ca-client register. Indeed the cert is issued only when fabric-ca-client enroll is run. Also for the bootstrap identity there is no fabric-ca-client register step in the docs.
Can someone provide an example illustrating what it is that register does which enroll cannot do?
REGISTER is used to make the CA aware of a new user that CAN be enrolled. You may set various options for the user (see fabric-ca-client register --help). Once you have registered the user, then the CA server will accept an enrolment API request for that user (given that the enrolment secret matches). This enrolment request includes the a CSR generated by the user. If the CA server accepts this enrolment request, it will return a signed x509 certificate. This will allow the user to communicate with the fabric network (where applicable).
Can someone provide an example illustrating what it is that register does which enroll cannot do?
To make this more clear:
ENROLL REQUIRES that a user already be registered.REGISTER DOES NOT provide a signed x509 certficate.