TopGit tracks hyperledger/fabric-ca on GitHub. The project has 453 stars.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
This is the Developer's Guide for Fabric CA, which is a Certificate Authority for Hyperledger Fabric.
Fabric CA can issue enrollment certificates and TLS certificates for Hyperledger Fabric deployments.
See the Fabric Getting Started Guide for information on how to install and use Fabric CA with Hyperledger Fabric sample networks.
See the Fabric CA User's Guide, Operations Guide, and Deployment Guide for detailed information on how to use and deploy Fabric CA.
The remainder of this guide is intended for developers contributing to Fabric CA.
Prerequisites
Go 1.25 installation or later
docker version 17.03 or later
docker-compose version 1.11 or later
Contribution guidelines
You are welcome to contribute to Fabric CA!
The following are guidelines to follow when contributing:
See the general information about contributing to fabric.
To run the unit tests manually:
# cd $GOPATH/src/github.com/hyperledger/fabric-ca
# 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.
WARNING: Running the unit-tests may fail due to too many open file descriptors.
Depending on where the failure occurs, the error message may not be obvious and may only say something similar to "unable to open database file".
Depending on the settings on your host, you may need to increase the maximum number of open file descriptors.
For example, the OSX default per-process maximum number of open file descriptors is 256.
You may issue the following command to display your current setting:
# ulimit -n
256
And the following command will increase this setting to 65536:
# ulimit -n 65536
Please note that this change is only temporary. To make it permanent, you will need to consult the documentation for your host operating system.
Package overview
cmd/fabric-ca-server contains the main for the fabric-ca-server command.
cmd/fabric-ca-client contains the main for the fabric-ca-client command.
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.
util/csp.go contains the Crypto Service Provider implementation.
lib/dbutil contains database utility functions.
lib/ldap contains LDAP client code.
lib/spi contains Service Provider Interface code for the user registry.
lib/tls contains TLS related code for server and client.
util contains various utility functions.
Additional info
FVT
See FVT tests for information on functional verification test cases.
Updating the cfssl vendored package
Following are the steps to update cfssl package using version 1.0.8 of govendor tool.
Remove cfssl from vendor folder
cd $GOPATH/src/github.com/hyperledger/fabric-ca/vendor
govendor remove github.com/cloudflare/cfssl/...
rm -rf github.com/cloudflare/cfssl/
Clone cfssl repo
cd $GOPATH/src/github.com/
mkdir cloudflare
cd cloudflare
git clone https://github.com/cloudflare/cfssl.git
Add cfssl from $GOPATH to the vendor folder
cd $GOPATH/src/github.com/hyperledger/fabric-ca/vendor
govendor add github.com/cloudflare/cfssl/^
You can optionally specify revision or tag to add a particular revision of code to the vendor folder
Remove sqlx package from cfssl vendor folder. This is because certsql.NewAccessor (called by fabric-ca) requires sqlx.db object to be passed from the same package. If we were to have sqlx package both in fabric-ca and cfssl vendor folder, go compiler will throw an error
Remove the packages that are added to the fabric-ca vendor folder that are not needed by fabric-ca
License
Hyperledger Project source code files are made available under the Apache License, Version 2.0 (Apache-2.0), located in the LICENSE file. Hyperledger Project documentation files are made available under the Creative Commons Attribution 4.0 International License (CC-BY-4.0), available at http://creativecommons.org/licenses/by/4.0/.
Yes — hyperledger/fabric-ca ships under the Apache-2.0 license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/hyperledger/fabric-ca.
What is hyperledger/fabric-ca?
hyperledger/fabric-ca (hyperledger/fabric-ca) is a Go project tracked by TopGit. The repository has 453 GitHub stars at the time of our last sync.
What license does hyperledger/fabric-ca use?
hyperledger/fabric-ca is released under the Apache-2.0 license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
Where can I see hyperledger/fabric-ca in action?
The project maintains a homepage at https://wiki.hyperledger.org/display/fabric. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about hyperledger/fabric-ca?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/hyperledger/fabric-ca is the definitive source.
Read full README in the tab above.
Want a second opinion on fabric-ca?
Ask an AI that can read this page — one click and you get its take on fabric-ca.
/fabric-ca