In previous years of the Spine programme, the NIS1 (INT) messaging certificate chain was installed in the other Spine test environments and certificate generation codes were provided separately from the endpoint registration (EPR) application. The T-Spine (TRAIN) environment was an exception, using its own unique certificates.
Combined MHS system and Accredited System (CMA) Endpoints
This is the most common endpoint type in the Path to Live environments, which consists of one Party Key and its related Accredited System Identifier (ASID). The information on the Party Key is identical to the information on the ASID and both are administrated together. It is not possible to have multiple ASIDs on a CMA Party Key and it is only possible for a product created as a ‘CMA’ product to be applied to a CMA Party Key and ASID.
This endpoint type will allow for the configuration of multiple ASIDs, with different MHS details and bindings, to be linked with a single party key. This involves creating the Party Key and each ASID individually and then associating the ASIDs with the Party Key. It is not possible to associate an ASID from a CMA endpoint with an MHS Party Key and it is only possible for a product created as an ‘MHS’ or ‘AS’ product to be applied to an MHS Party Key and ASID.
Introduction of Spine CIS
With the introduction of Spine CIS and specifically the transfer of NIS1 PKI to Spine CIS, messaging certificates are no longer sourced from BT Spine.
A process has been identified using the Spine CIS ‘endpoint Registration Service’ application and this is described in this document.