This process describes signing a contract package and storing it in the Contract Certificate Pool(CCP).
If the MO uses its own Certificate Authority, it must create a contract data with the following parts:
- contractSignatureCertChain
- dhPublicKey
- contractSignatureEncryptedPrivateKey,
- EMAID
The created contract data must be signed by the CPS, this signature will be used as a trust anchor. For that, MOs have two possibilities:
- Using createAndForwardSignedContratData interface for signing and storing signed contract data in the CCP;
- Or sending the contract data with createSignedContractData interface, where the contract data will be signed and the MO will receive the signed contract data back after the signing by the CPS. Using this case the contract certificate will not be automatically stored on the CCP, for that, the MO must call the endpoint: AddSignedContractData on the CCP.