+
+
+
+
+
+
+ The certificate signing requests model contains the essential information needed to request specific certificates for a unique ECU component via a Certificate Signing Request (CSR) and to validate and certificate the ECU against this data.
+
+
+
+
+
+ Overview
+
+
+
+
+
+
+
+ 
+
+
+
+
+
+
+
+
+
+
+Properties
+
+
+
+
+
+
+Describes one or more Certificate Singing Requests (CSR). Each set entry contains additional information (e.g. subjectCommonName, subjectLocality, etc.) in readable form, which is otherwise part of the encrypted CSR.
+
+ Certificate Signing Request List
+
+
+
+
+
+ Name
+ certificateSigningRequestList
+
+
+
+
+ Characteristic
+
+
+
+
+
+
+ Set
+
+
+ Has no order
+
+
+
+ Duplicates not allowed
+
+
+
+ Optional
+
+ Yes
+
+
+
+ In payload
+
+ Yes
+
+
+
+
+Payload key
+ certificateSigningRequestList
+
+
+
+
+
+
+ Entities
+
+
+
+
+ Certificate Signing Requests Entity
+
+ The Entity of a certificate signing requests to additionally structure the set.
+
+
+
+
+Properties
+
+
+
+
+
+
+Describes the common name on where the certificate is requested.
+
+ Subject Common Name
+
+
+
+
+
+ Name
+ subjectCommonName
+
+
+
+ Characteristic
+
+
+
+
+
+
+
+ Type http://www.w3.org/2001/XMLSchema#string
+
+
+
+
+
+ Example
+ IPsec-Internal
+
+
+
+ Optional
+
+ No
+
+
+
+ In payload
+
+ Yes
+
+
+
+
+Payload key
+ subjectCommonName
+
+
+
+
+
+
+Provides information about the specific type of the ECU that will be certified.
+
+The value for the subjectLocality is always the same for an ECU and its attached CSRs, but is required to additionally validate each individual CSR.
+
+ Subject Locality
+
+
+
+
+
+ Name
+ subjectLocality
+
+
+
+ Characteristic
+
+
+
+
+
+
+
+ Type http://www.w3.org/2001/XMLSchema#string
+
+
+
+
+
+ Example
+ ATM--02
+
+
+
+ Optional
+
+ No
+
+
+
+ In payload
+
+ Yes
+
+
+
+
+Payload key
+ subjectLocality
+
+
+
+
+
+
+A CSR (Certificate Signing Request) is a 64-based PEM formatted and encrypted message to request and receive a digital certificate. The CSR validates the information required by a specific certification authority (CA) to issue the associated digital certificate.
+
+The CSR consists of encrypted data, which can include, for example, basic information about the ECU and its manufacturer (common name, company, organizational unit, country, city/town, etc.), information about the public key attached to the certificate, as well as information on the key type and length.
+
+ Certificate Signing Request
+
+
+
+
+
+ Name
+ certificateSigningRequest
+
+
+
+ Characteristic
+
+
+
+
+
+
+
+ Type http://www.w3.org/2001/XMLSchema#string
+
+
+
+
+
+ Example
+ MIIC2TCCAToCAQAwgZwxEzARBgNVBAgTClByb2R1Y3Rpb24xDDAKBgNVBAcMA0FUTTESMBAGA1UEChMJQk1XIEdyb3VwMRcwFQYDVQQLEw5WZWhpY2xlUEtJLUVDVTEXMBUGA1UEAxMOSVBzZWMtaW50ZXJuYWwxMTAvBgNVBAUTKEVDVS1VSUQ6QzAwMDgyNDI3MUREQTYwMDAwMDAwMDAwMjdBQTg0MjQwdjAQBgcqhkjOPQIBBgUrgQQAIgNiAAShNm4y5Mdzu4b9xDW3TfBZr
+
+
+
+ Optional
+
+ No
+
+
+
+ In payload
+
+ Yes
+
+
+
+
+Payload key
+ certificateSigningRequest
+
+
+
+
+
+
+The serial number of the assembly part generated by the manufacturer that is used to identify the ECU component in a unique way. The subject serial number is identical to the serial number (partInstanceId) specified in the aspect model SerialPart.
+
+The value for the subjectSerialNumber is always the same for an ECU and its attached CSRs, but is required to additionally validate each individual CSR.
+
+ Subject Serial Number
+
+
+
+
+
+ Name
+ subjectSerialNumber
+
+
+
+ Characteristic
+
+
+
+
+
+
+
+ Type http://www.w3.org/2001/XMLSchema#string
+
+
+
+
+
+ Example
+ ECU-UID:SN12345678
+
+
+
+ Optional
+
+ No
+
+
+
+ In payload
+
+ Yes
+
+
+
+ Payload key
+ subjectSerialNumber
+
+
+
+Reference
+
+
+ -
+
- https://github.com/eclipse-tractusx/sldt-semantic-models/tree/main/io.catenax.serial_part +
+ Third party licenses
+
+
+
+