Hyperledger Composer Environment Orgs and Users

Q

What Orgs and Users are included in my Hyperledger Composer Environment?

✍: FYIcenter.com

A

The fabric-dev-servers.tar.gz package includes two default organizations and one admin user for each organization:

org1.example.com - "org1.example.com" is the organization owns the peer node "peer0.org1.example.com". "org1.example.com" has its own CA (Certificate Authority) and uses the following directory to store its certificates:

$ cd fabric-dev-servers/fabric-scripts/hlfv12/composer/crypto-config 
$ cd peerOrganizations/org1.example.com/users/Admin@org1.example.com/smp

$ ls -l 
drwxr-xr-x 2 fyicenter Apr  1 01:59 admincerts
drwxr-xr-x 2 fyicenter Apr  1 01:59 cacerts
drwxr-xr-x 2 fyicenter Apr  1 01:59 keystore
drwxr-xr-x 2 fyicenter Apr  1 01:59 signcerts
drwxr-xr-x 2 fyicenter Apr  1 01:59 tlscacerts

The "admincerts" directory stores the admin user certificate:

$ ls -l admincerts/
-rw-r--r-- 1 fyicenter 790 Sep 29  2018 Admin@org1.example.com-cert.pem

If you open the admin user certificate and decode it, you will see:

Subject: 
   Common Name (CN): Admin@org1.example.com
   Locality Name (L): San Francisco
   State or Province Name (ST): California
Issuer: 
   Common Name (CN): ca.org1.example.com
   Organization Name (O): org1.example.com
   Locality Name (L): San Francisco
   State or Province Name (ST): California
   Country Name (C): US
Valid From: Mon, 26 Jun 2017 12:49:26 +0000 
Valid To: Thu, 24 Jun 2027 12:49:26 +0000 

Of course, the "cacerts" directory stores the CA root certificate:

$ ls -l cacerts/
-rw-r--r-- 1 fyicenter 843 Sep 29  2018 ca.org1.example.com-cert.pem

The private keys are stored in the "keystore" directory:

$ ls -l keystore/
-rw-r--r-- 1 fyicenter 241 Sep 29  2018 114aab0e76bf0c78308f89efc4b8c9423e31568da0c340ca187a9b17aa9a4457_sk

The default admin user of "org1.example.com" has also been configured with an enrollment ID of "admin" and an enrollment secret of "adminpw". Note that, this admin user does not have permission to deploy business networks to the environment.

example.com - "example.com" is the organization owns the orderer node "orderer.example.com". "example.com" has its own CA (Certificate Authority) and uses the following directory to store its certificates:

$ cd fabric-dev-servers/fabric-scripts/hlfv12/composer/crypto-config 
$ cd ordererOrganizations/example.com/users/Admin@example.com/smp

$ ls -l 
drwxr-xr-x 2 fyicenter Apr  1 01:59 admincerts
drwxr-xr-x 2 fyicenter Apr  1 01:59 cacerts
drwxr-xr-x 2 fyicenter Apr  1 01:59 keystore
drwxr-xr-x 2 fyicenter Apr  1 01:59 signcerts
drwxr-xr-x 2 fyicenter Apr  1 01:59 tlscacerts

The "admincerts" directory stores the admin user certificate:

$ ls -l admincerts/
-rw-r--r-- 1 fyicenter 769 Sep 29  2018 Admin@example.com-cert.pem

$ ls -l cacerts/
-rw-r--r-- 1 fyicenter 818 Sep 29  2018 ca.example.com-cert.pem

 

Hyperledger Composer Environment Channels

Hyperledger Composer Environment Components

Explorer Hyplerledger Composer Environment

⇑⇑ Hyperledger Composer Tutorials

2020-07-14, 190👍, 0💬