Skip to content

Latest commit

 

History

History
53 lines (27 loc) · 2.41 KB

04_contract-certificate-pool.md

File metadata and controls

53 lines (27 loc) · 2.41 KB

Contract Certificate Pool

The CCP stores the signed contract data from the MOs, and provides it for the CPOs and OEMs backend. The CPO's backend can request a signed contract using the certificateInstallationRequest, as defined on ISO 15118-2:2014.

The CPS' signed contract data will be stored in the CCP, and assigned to their respective PCID. The CCP also enables Multiple contracts storing for each PCID.

The CCP keeps contracts of each MO separated. The defined access rules prevent unauthorized requests to others MOs contracts it means that each MO only can manage (create/update/delete) contracts of their own company.

The Ecosystem Administration creates a node for each MO after the provider ID confirmation from the issuing authority.

API

The Contract Certificate Pool offers a REST API supporting registered contract certificate requests.

All CCP API's documentation are available at ccp.v1.json.

Processes

The Contract Certificate Pool (CCP) is involved in multiple processes across the ecosystem. The Direct Processes are described bellow:

1. Publish a Contract Certificate

The Contract Certificate pool can receive contracts by two means: 1- Contracts forwarded by the CPS 2- Added contracts by the MOs

Publishing a Contract Certificate in the pool can trigger an instant push notification to the OEM enrolled in the WMI corresponding to the contract's PCID. See Webhooks Service

2. Update a Contract Certificate

In case an MO needs to renew a Contract Certificate, they may do so by sending an updated Certificate to the pool.

The update process overwrites the existing Contract Certificate with the same EMAID.

An update of a Contract Certificate in the pool can trigger an instant push notification to the OEM enrolled in the WMI corresponding to the contract's PCID. See Webhooks Service

3. Delete a Contract Certificate

In case the Contract Certificate under one EMAID needs be removed from the ecosystem, the MO that owns it may delete it from the pool.

A deletion of a contract certificate in the pool can trigger an instant push notification to the OEM enrolled in the WMI corresponding to the contract's PCID. See Webhooks Service

Data Cleansing

The Contract Certificate Pool should be cleaned regularly.