Updating README

README.md

@@ -28,6 +28,7 @@ It is time to run the CLI (Client helper executable script) to setup your DID an
 2. Before running the CLI make sure to execute this in a linux bash terminal: ./client-helper.sh
 3. Now enter the URL of the lacpass-lacchain verified in the previous section
 4. The following menu is presented:
+
 ![](https://github.com/lacchain/LACPass-client/blob/master/docs/examples/CLIMainMenu.png)
 
 5. If you don't have a PKI or don't have any signing key to attest health certificates then you can create a Self-Signed Certificate "SSC". Type that if needed and enter the required information.
@@ -50,8 +51,59 @@ Just as a reference, the created DID (Decentralized Identifier) will be saved in
 
 8. Create a manager. Type "CM" in the CLI main menu.
 *  Enter the number of days to consider the manager to be created as valid, for example: 1000; as shown in the following figure. Suggested: do not enter a number less than 365 days.
-
 ![](https://github.com/lacchain/LACPass-client/blob/master/docs/examples/creatingManager.png)
+* A successful response will be something like:  
+* Type 'exit' to end the setup process:
+
+After having run the previous steps, you will have the following information inside the directory /lacchain-setup-helper:
+* A did.txt file which contains the DID for your organization. Keep it in a place you can always access it.
+* The /certs directory, containing the SCA and DSC subdirectories.
+
+### Sharing onboarding material 
+
+Now you are ready to share onboarding information with the committee. 
+
+1. Start the CLI again
+2. In options choose "GCM" (Get Current Manager) to get the entity and manager details
+![](https://github.com/lacchain/LACPass-client/blob/master/docs/examples/GCM.png)
+a. copy the content in a text file, give it a nmae like "Entity-manager_Details.txt"
+
+3. Pack the following information in a zip file:
+
+a. Entity-Manager-Details.txt you just got in the previous step
+b. The SCA.crt file, located inside the directory /lacchain-setup-helper/certs/SCA/SCA.crt
+c. Identifying information
+	i. Legal Name
+	ii. FHIR-URL
+	iii. Country/Country Code
+
+4. Send the information via email to [email protected] and [email protected]
+
+### Sending Certificates wrapped as Verifiable Credentials
+
+In this section you will learn how to use the send verifiable credentials endpoint exposed by the lacpass-lacchain component. If you successfully followed the previous steps, you are ready to send health certificates to your users. 
+
+As explained in “Verify Service availability” lacpass-lacchain runs on port 3010 by default. To send DDCCCoreDataSet health certificates you can use the postman tool:
+
+* Method: POST
+* http://localhost:3010/api/v1/verifiable-credential/ddcc/send (update the host properly in case you are not accessing via localhost)
+* The required payload to send has the following structure:
+	{ 
+	 "bundle":
+			{
+			 "entry": 
+			  ["string"]		
+			},
+	 "issuerDid": "string",
+	 "receiverDid": "string"
+	}
+
+Where:
+* bundle: FHIR bundle, just copy and paste the full FHIR bundle
+* IssuerDid: Issuer DID, this is the decentralized identifier you created in the section Running Setup/Onboard steps in step 6 and that is available in the lacchain-setup-helper/did.txt file
+* receiverDid: This is the Receiver DID (the patient/individual receiving the certificate) will share with you to receive the issued credential in their wallet. Patients/individuals can easily get their unique identifier (DID) after setting up the wallet available at https://lacpass-openprotest-wallet.lacchain.net/
+
+NOTE: A full example with the required payload is available at https://github.com/lacchain/LACPass-client/blob/master/docs/Credential-Sending.md