"PeerAdmin@hlfv1" - Peer Admin Access Card

Q

What is Peer Admin Access Card "PeerAdmin@hlfv1"?

✍: FYIcenter.com

A

"PeerAdmin@hlfv1" is a special Business Network Card that has special permission to deploy new Business Network to the peer node, "peer0.org1.example.com" in your Hyperledger Composer Developer Environment?

"PeerAdmin@hlfv1" card can be created with the "createPeerAdminCard.sh" script:

$ cd fabric-dev-servers
$ ./createPeerAdminCard.sh

The following Business Network Cards are available:

Connection Profile: hlfv1
┌─────────────────┬───────────┬──────────────────┐
│ Card Name       │ UserId    │ Business Network │
├─────────────────┼───────────┼──────────────────┤
│ PeerAdmin@hlfv1 │ PeerAdmin │                  │
└─────────────────┴───────────┴──────────────────┘

Like all other Business Network cards, "PeerAdmin@hlfv1" is stored in wallet directory, "~/.composer/cards", on your local computer:

$ cd ~/.composer/cards

$ ls -l 
drwxr-x--- 3 fyicenter 4096 Apr  1 20:00 PeerAdmin@hlfv1

$ ls -l PeerAdmin@hlfv1
-rw-r----- 1 fyicenter  690 Apr  1 20:00 connection.json
drwxr-x--- 2 fyicenter 4096 Apr  1 20:00 credentials
-rw-r----- 1 fyicenter   73 Apr  1 20:00 metadata.json

$ ls -l PeerAdmin@hlfv1/credentials/
-rw-r----- 1 fyicenter 790 Apr  1 20:00 certificate
-rw-r----- 1 fyicenter 241 Apr  1 20:00 privateKey

"connection.json" is the connection profile, which contains information about the peer node and channel.

{
    "name": "hlfv1",
    "x-type": "hlfv1",
    "x-commitTimeout": 300,
    "version": "1.0.0",
    "client": {
        "organization": "Org1",
        "connection": {...}
    },
    "channels": {
        "composerchannel": {
            "orderers": ["orderer.example.com"],
            "peers": {"peer0.org1.example.com": {}}
        }
    },
    "organizations": {
        "Org1": {
            "mspid": "Org1MSP",
            "peers": ["peer0.org1.example.com"],
            "certificateAuthorities": ["ca.org1.example.com"]
        }
    },
    "orderers": {
        "orderer.example.com": {
            "url": "grpc:\/\/localhost:7050"
        }
    },
    "peers": {
        "peer0.org1.example.com": {
            "url": "grpc:\/\/localhost:7051"
        }
    },
    "certificateAuthorities": {
        "ca.org1.example.com": {
            "url": "http:\/\/localhost:7054",
            "caName": "ca.org1.example.com"
        }
    }
}

"credentials" is the directory where certificate and private key are stored.

"metadata.json" contains information of user name and roles:

{"version":1,
 "userName":"PeerAdmin",
 "roles":["PeerAdmin","ChannelAdmin"]
}

Note that "PeerAdmin@hlfv1" card is really represents the default admin user, "Admin@org1.example.com", registered in the "org1.example.com" peer organization.

 

Create "PeerAdmin@hlfv1" Card Manually

Hyperledger Composer Environment Channels

Explorer Hyplerledger Composer Environment

⇑⇑ Hyperledger Composer Tutorials

2020-07-14, 203👍, 0💬