How to add enrollments to REST proxy in Oracle Blockchain Cloud

Add Enrollments to the REST Proxy

You can add Hyperledger Fabric enrollments to the  REST proxy. Enrollments allow users to call the REST proxy without an  enrollment certificate.

Adding an enrollment to the REST Proxy creates a new user role in Oracle Identity Cloud Service. This role is: RESTPROXY#_USER_${enrollment_name}                      

After the enrollment is created in the console, the Administrator uses Oracle Identity Cloud Service to assign the required users to this role.                       

For information about how users access the REST resources, see REST API for Oracle Autonomous Blockchain Cloud Service.                      

A new user role called RESTPROXY#_USER_${enrollment_name} is created in Oracle Identity Cloud Service and is now ready for the Administrator to assign users to it. See Add Hyperledger Fabric Enrollments to a REST Proxy in Administering Oracle Autonomous Blockchain Cloud Service.                                     

Add User to the enrollment

Assign a user to the  role called RESTPROXY#_USER_${enrollment_name}  - RESTPROXY#_USER_$producer

Deploy a Hyperledger Fabric blockchain network in Oracle Blockchain Cloud Service

I am not going to go through all the process of creating the
blockchain instances and I am going to focus on the process of
creating the HLF network, pariring the participant instance
with the founder organization network.

The process of creation OBC instances it is well explained in the
documentation.

https://docs.oracle.com/en/cloud/paas/blockchain-cloud/administer/create-oabcs-instance.html#GUID-C24F59D7-E81E-4527-93AD-E3DDCEA13704

There are two types of OABCS instances you can provision:

Founder organization: a complete blockchain environment,

including a new network to which participants can join later on.

Participant instance: if there is already a founder organization you

want to join, you can create a participant instance if your

credentials provide you with access to the network.

On creating the Founder you will need the “Create a new Network”
checked.

The network has been created with two instances: the "matrix" as a founder and the "producer" as a provider. Let's open the two instances consoles from the hamburger at the right hand side

Add OBCS Instance as a Network Participant

When you get into the "producer" instance it propose you to join to an already existing network.

Here are the screenshots. It is self explained through the UI. I will just annotate to which instance belongs the UI.

Step 1.1. Producer Instance

Step 1.2. "Producer" Instance. Export Certificate.

Step 1.3.1. Founder. Add Organization.

Step 1.3.2. Founder. Add "Producer" Instance Certification

Step 1.3.3. Founder. Add Organization successfully completed

Step 1.3.4. Founder. Organization added to the founder network.

Step 1.4.1. Founder. Export Order Settings.

Step 1.4.2."Producer" Instance. Import founder orderer settings.

Step 1.4.2."Producer" Instance.  Successfully imported founder orderer settings.

Step 1.5. "Producer" Instance is now a participant in the Parent blockchain network

Create a new channel

Step 2.1. Founder. Create a new channel.

Step 2.2. Founder Instance. Details on creating a new channel "logistica".

Step 2.2. Founder Instance. Channel "logistica" created with two founder peers participating in the channel.

Step 2.3. "producer" Instance is part of the channel "logistica" but still any peer has been added.

Step 2.4. Add "producer" Instance's  peers to the channel "logistica"

Step 2.5. Choose the "producer" Instance's  peers to add

Step 2.5. "producer" Instance's  peers already added