SNIP_CLASSIC_KEYM_FIGURE_Figure_7_3

Figure 7.3: Exemplary configuration of a certificate chain in a hierarchy with references to CSM jobs and keys. [SWS_KeyM_00025] Upstream requirements: SRS_CryptoStack_00120 ⌈A certificate is stored for verification with the call of the function KeyM_SetCertificate(). The certificate will be placed in the preconfigured storage class of the KeyMCertificate/ KeyMCertificateStorage.⌋ Note: Such a certificate is typically placed in RAM and is not intended to be used for permanent storage. KeyM_SetCertificate() is just used for the verification of a presented certificate. It is not intended to be used for permanent storage like for example the Root certificate. For operation to store a certificate permanently , the function KeyM_ ServiceCertificate{ByCertId}() shall be used. Certificates can be represented in different formats. [SWS_KeyM_00175] Upstream requirements: SRS_CryptoStack_00112 ⌈The configuration shall support three different formats, [8] the X.509, CVC and CRL. ⌋ Key elements that are assigned to certificates can be categorized into basic elements of the structure. This is configured with KeyMCertificateElement/KeyMCertificateElementOfStructure. The following tables give correspondences of the enum values of KeyMCertificateElementOfStructure to the naming convention of the respective specifications.