This is the Developer's Guide for Fabric CA, which is a Certificate Authority for Hyperledger Fabric.

See User's Guide for Fabric CA for information on how to use Fabric CA.

• Go 1.7+ installation or later
• GOPATH environment variable is set correctly
• docker version 17.03 or later
• docker-compose version 1.11 or later
• A Linux Foundation ID (see create a Linux Foundation ID)

You are welcome to contribute to Fabric CA!

The following are guidelines to follow when contributing:

1. See the general information about contributing to fabric.

2. To set up your development environment for doing common development tasks, see bash_profile. This contains variables and functions which can be copied directly into your .bash_profile file. Even if you do not use bash, you should still find the functions instructive. For example:
   a. clone - pulls the latest fabric-ca code from gerrit and places it based on your GOPATH setting
   b. cdr - cd to the fabric-ca repository root, which is equivalent to "cd $GOPATH/src/github.com/hyperledger/fabric-ca"
   c. gencov - generates a test coverage report

3. To run the unit tests manually:

   # cdr
   # make unit-tests
   

   The test coverage for each package must be 75% or greater. If this fails due to insufficient test coverage, then you can run gencov to get a coverage report to see what code is not being tested. Once you have added additional test cases, you can run go test -cover in the appropriate package to see the current coverage level.

1. cmd/fabric-ca-server contains the main for the fabric-ca-server command.
2. cmd/fabric-ca-client contains the main for the fabric-ca-client command.
3. lib contains most of the code.
   a) server.go contains the main Server object, which is configured by serverconfig.go.
   b) client.go contains the main Client object, which is configured by clientconfig.go.
4. lib/csp contains some functions related to the Crypto Service Provider.
5. lib/dbutil contains database utility functions.
6. lib/ldap contains LDAP client code.
7. lib/spi contains Service Provider Interface code for the user registry.
8. lib/tls contains TLS related code for server and client.
9. util contains various utility functions.

To enable profiling on the server, set the FABRIC_CA_SERVER_PROFILE_PORT environment variable to a valid, available port number and start the server. The server will start listening for profile requests at the specified port. Then run go tool pprof with server's profiling URL (http://:/debug/pprof/<profile|heap|block>) as an argument, it will download and examine a live profile.

To enable profiling on the client, set the FABRIC_CA_CLIENT_PROFILE_MODE environment variable to either "heap" or "cpu" to enable heap, cpu profiling respectively. A file containing profiling data is created in the present working directory of the client. Heap profiling data is written to mem.pprof and cpu profiling data is written to cpu.pprof. You can run go tool pprof <client executable> <profiling file> to analyze the profiling data.

Run go tool pprof -h to view the options supported by the pprof tool. For more information on profiling, see https://blog.golang.org/profiling-go-programs

See FVT tests for information on functional verification test cases.