hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.7 EU qualified validation service determination
| |
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.7.1 Description
|
The procedure specified in clause 4.7 allows determining whether the signer identified in the certificate supporting the validation of the digital signature of a trust service output is confirmed by the applicable EUMS trusted list to have been, at a specific date and time, an EU qualified trust service provider for the provision of a qualified validation service for qualified electronic signatures and/or for the provision of a qualified validation service for qualified electronic seals. NOTE: The verification whether the trust service output is indeed a signature validation report attesting the result of the validation process of an EU qualified electronic signature or of an EU qualified electronic seal is out of scope of the present procedure.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.7.2 Inputs
|
Name Description of inputs CERT X.509 certificate for which the information is to be obtained (e.g. a ds:X509Certificate value of a ds:KeyInfo of the ds:Signature from the corresponding trust service output) Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1].
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.7.3 Outputs
|
Name Description QVSO-Results A set of indications of the EU qualified status of the QTSP/QTS identified through the subjectName attribute of CERT, which contains one or more of the following values: a) "Not_Qualified_For_eSig" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to not have been, at Date-time, an EU qualified trust service provider for the provision of a qualified validation service for qualified electronic signatures; b) "Not_Qualified_For_eSeal" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to not have been, at Date-time, an EU qualified trust service provider for the provision of a qualified validation s ervice for qualified electronic seals; c) "Qualified_For_eSig" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to have been, at Date-time, an EU qualified trust service provider for the provision of a qualified validation service for qualified electronic signatures; d) "Qualified_For_eSeal" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to have been, at Date-time, an EU qualified trust service provider for the provision of a qualified validation service for qualified electronic seals; e) "Indeterminate" to indicate that the EUMS trusted list from CC cannot be used to confirm that the signer identified in the CERT has been, at Date-time, an EU qualified trust service provider for the provision of a qualified validation service for qualified electronic signatures or for the provision of a qualified validation service for qualified electronic seals. QVSO-Status The status indication of the process. QVSO-Sub-Status A list of indications supplementing QVSO-Status indication. CC The country code of the EUMS trusted list being used to obtain the above listed three other outputs. OUT-4.7.3-01: All above listed output variables shall be initialized to void. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 41
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.7.4 Processing
|
PRO-4.7.4-01: If Date-time is before "2016-06-30T22:00:00Z", then: a) the processing shall set QVSO-Status to the value "PROCESS_PASSED"; b) the processing shall set QVSO-Results to the set of values "Not_Qualified_For_eSig" and "Not_Qualified_For_eSeal"; and c) the processing shall stop the process. PRO-4.7.4-02: The processing shall set CC to the country code value of the countryName attribute of the subjectName field of the certificate provided in CERT, in capital letters in accordance with the ISO 3166-1 [2] Alpha 2 country code, with, when applicable: a) the country code value "GB" being converted to "UK"; b) the country code value "GR" being converted to "EL". PRO-4.7.4-03: The processing shall set TLS-Sti to the value "http://uri.etsi.org/TrstSvc/Svctype/QESValidation/Q" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.7.4-04: The processing shall run the process described in clause 4.3 of the present document, passing the following inputs to the process: a) CERT; b) TLS-Sti; c) Date-time; d) CC. PRO-4.7.4-05: If the output SI-Status of the process run in PRO-4.7.4-04 has the value "PROCESS_FAILED", then: a) the processing shall set QVSO-Status to the value "PROCESS_FAILED"; b) the processing shall set QVSO-Sub-Status to the set of values from SI-Status and SI-Sub-Status; and c) the processing shall stop the process. PRO-4.7.4-06: If the output SI-Results of the process run in PRO-4.7.4-04 is void, then: a) the processing shall set QVSO-Status to the value "PROCESS_PASSED"; b) the processing shall set QVSO-Results to the value "Indeterminate"; c) the processing shall set QVSO-Results to the set of values "Not_Qualified_For_eSig" and "Not_Qualified_For_eSeal"; and d) the processing shall stop the process. PRO-4.7.4-07: If the output SI-Results of the process run in PRO-4.7.4-04 includes more than one tuple for which the SI-at-Date-time respective parts include different values for their 'Service current status' or 'Service previous status' field, then: a) the processing shall set QVSO-Status to the value "PROCESS_FAILED"; b) the processing shall set QVSO-Results to the value "Indeterminate"; c) the processing shall set QVSO-Sub-Status to the value "ERROR_INCONSISTENCY_IN_TL_ON_VSO- CERT_STATUS"; and ETSI ETSI TS 119 615 V1.2.1 (2023-06) 42 d) the processing shall stop the process. PRO-4.7.4-08: If the output SI-Results of the process run in PRO-4.7.4-04 includes more than one tuple for which the SI-at-Date-time respective parts include different public key values for their 'Service digital identifier' field (see clause 5.5.3 of ETSI TS 119 612 [1]), then the processing shall add to QVSO-Sub-Status the value "WARNING_DUPLICATION_OF_SERVICE_INFORMATION_IN_TL_REGARDING_VSO-CERT". PRO-4.7.4-09: If the organizationName attribute of the subjectName field of the certificate provided in CERT is not matching one of the values of TSP-Name or TSP-Trade-Name of the output SI-Results of the process run in PRO-4.7.4-04, then: a) the processing shall set QVSO-Status to the value "PROCESS_FAILED"; b) the processing shall set QVSO-Results to the value "Indeterminate"; c) the processing shall set QVSO-Sub-Status to the value "ERROR_TSP_NAME_INCONSISTENCY_BETWEEN_CERT_AND_TL"; and d) the processing shall stop the process. PRO-4.7.4-10: If the 'Service current status' or 'Service previous status' field(s) of the SI-at-Date-time part(s) of the output SI-Results of the process run in PRO-4.7.4-04 has (have) the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted": a) then: 1) the processing shall set QVSO-Status to the value "PROCESS_PASSED"; 2) if one of these SI-at-Date-time respective parts include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) including the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures": i) then the processing shall add to QVSO-Results the value "Qualified_For_eSig"; ii) else the processing shall add to QVSO-Results the value "Not_Qualified_For_eSig"; 3) if one of these SI-at-Date-time respective parts include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) including the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSeals": i) then the processing shall add to QVSO-Results the value "Qualified_For_eSeal"; ii) else the processing shall add to QVSO-Results the value "Not_Qualified_For_eSeal"; and 4) the processing shall stop the process. b) else: 1) the processing shall set QVSO-Status to the value "PROCESS_PASSED"; 2) the processing shall set QVSO-Results to the set of values "Not_Qualified_For_eSig" and "Not_Qualified_For_eSeal"; and 3) the processing shall stop the process. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 43
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.8 EU qualified preservation service determination
| |
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.8.1 Description
|
The procedure specified in clause 4.8 allows determining whether the signer identified in the certificate supporting the validation of the digital signature of a trust service output is confirmed by the applicable EUMS trusted list to have been, at a specific date and time, an EU qualified trust service provider for the provision of a qualified preservation service for qualified electronic signatures and/or for the provision of a qualified preservation service for qualified electronic seals. NOTE: The present process is only applicable when the qualified trust service provider providing a qualified preservation service for qualified electronic signatures and/or for qualified electronic seals is making use of PKI technology (e.g. for digitally signing evidences, attestations, reports) and the related PKI certificate is published in the applicable EUMS trusted list.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.8.2 Inputs
|
Name Description of inputs CERT X.509 certificate for which the information is to be obtained (e.g. a ds:X509Certificate value of a ds:KeyInfo of the ds:Signature from the corresponding trust service output) Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1].
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.8.3 Outputs
|
Name Description QPSO-Results A set of indications of the EU qualified status of the QTSP/QTS identified through the subjectName attribute of CERT, which contains one or more of the following values: a) "Not_Qualified_For_eSig" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to not have been, at Date-time, an EU qualified trust service provider for the provision of a qualified preservation service for qualified electronic signatures; b) "Not_Qualified_For_eSeal" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to not have been, at Date-time, an EU qualified trust service provider for the provision of a qualified preservation service for qualified electronic seals; c) "Qualified_For_eSig" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to have been, at Date-time, an EU qualified trust service provider for the provision of a qualified preservation service for qualified electronic signatures; d) "Qualified_For_eSeal" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to have been, at Date-time, an EU qualified trust service provider for the provision of a qualified preservation service for qualified electronic seals; e) "Indeterminate" to indicate that the EUMS trusted list from CC cannot be used to confirm that the signer identified in the CERT has been, at Date-time, an EU qualified trust service provider for the provision of a qualified preservation service for qualified electronic signatures or for the provision of a qualified preservation service for qualified electronic seals. QPSO-Status The status indication of the process. QPSO-Sub-Status A list of indications supplementing QPSO-Status indication. CC The country code of the EUMS trusted list being used to obtain the above listed three other outputs. OUT-4.8.3-01: All above listed output variables shall be initialized to void. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 44
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.8.4 Processing
|
PRO-4.8.4-01: If Date-time is before "2016-06-30T22:00:00Z", then: a) the processing shall set QPSO-Status to the value "PROCESS_PASSED"; b) the processing shall set QPSO-Results to the set of values "Not_Qualified_For_eSig" and "Not_Qualified_For_eSeal"; and c) the processing shall stop the process. PRO-4.8.4-02: The processing shall set CC to the country code value of the countryName attribute of the subjectName field of the certificate provided in CERT, in capital letters in accordance with the ISO 3166-1 [2] Alpha 2 country code with, when applicable: a) the country code value "GB" being converted to "UK"; b) the country code value "GR" being converted to "EL". PRO-4.8.4-03: The processing shall set TLS-Sti to the value "http://uri.etsi.org/TrstSvc/Svctype/PSES/Q" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.8.4-04: The processing shall run the process described in clause 4.3 of the present document, passing the following inputs to the process: a) CERT; b) TLS-Sti; c) Date-time; d) CC. PRO-4.8.4-05: If the output SI-Status of the process run in PRO-4.8.4-04 has the value "PROCESS_FAILED", then: a) the processing shall set QPSO-Status to the value "PROCESS_FAILED"; b) the processing shall set QPSO-Results to the value "Indeterminate"; c) the processing shall set QPSO-Sub-Status to the set of values from SI-Status and SI-Sub-Status; and d) the processing shall stop the process. PRO-4.8.4-06: If the output SI-Results of the process run in PRO-4.8.4-04 is void, then: a) the processing shall set QPSO-Status to the value "PROCESS_PASSED"; b) the processing shall set QPSO-Results to the set of values "Not_Qualified_For_eSig" and "Not_Qualified_For_eSeal"; and c) the processing shall stop the process. PRO-4.8.4-07: If the output SI-Results of the process run in PRO-4.8.4-04 includes more than one tuple for which the SI-at-Date-time respective parts include different values for their 'Service current status' or 'Service previous status' field, then: a) the processing shall set QPSO-Status to the value "PROCESS_FAILED"; b) the processing shall set QPSO-Results to the value "Indeterminate"; c) the processing shall set QPSO-Sub-Status to the value "ERROR_INCONSISTENCY_IN_TL_ON_PSO- CERT_STATUS"; and ETSI ETSI TS 119 615 V1.2.1 (2023-06) 45 d) the processing shall stop the process. PRO-4.8.4-08: If the output SI-Results of the process run in PRO-4.8.4-04 includes more than one tuple for which the SI-at-Date-time respective parts include different public key values for their 'Service digital identifier' field (see clause 5.5.3 of ETSI TS 119 612 [1]), then the processing shall add to QPSO-Sub-Status the value "WARNING_DUPLICATION_OF_SERVICE_INFORMATION_IN_TL_REGARDING_PSO-CERT". PRO-4.8.4-09: If the organizationName attribute of the subjectName field of the certificate provided in CERT is not matching one of the values of TSP-Name or TSP-Trade-Name of the output SI-Results of the process run in PRO-4.7.4-04, then: a) the processing shall set QPSO-Status to the value "PROCESS_FAILED"; b) the processing shall set QPSO-Results to the value "Indeterminate"; c) the processing shall set QPSO-Sub-Status to the value "ERROR_TSP_NAME_INCONSISTENCY_BETWEEN_CERT_AND_TL"; and d) the processing shall stop the process. PRO-4.8.4-10: If the 'Service current status' or 'Service previous status' field(s) of the SI-at-Date-time part(s) of the output SI-Results of the process run in PRO-4.8.4-04 has the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted": a) then: 1) the processing shall set QPSO-Status to the value "PROCESS_PASSED"; 2) if one of these SI-at-Date-time respective parts include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) including the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures": i) then the processing shall add to QPSO-Results the value "Qualified_For_eSig"; ii) else the processing shall add to QPSO-Results the value "Not_Qualified_For_eSig"; 3) if one of these SI-at-Date-time respective parts include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) including the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSeals": i) then the processing shall add to QPSO-Results the value "Qualified_For_eSeal"; ii) else the processing shall add to QPSO-Results the value "Not_Qualified_For_eSeal"; and 4) the processing shall stop the process. b) else: 1) the processing shall set QPSO-Status to the value "PROCESS_PASSED"; 2) the processing shall set QPSO-Results to the set of values "Not_Qualified_For_eSig" and "Not_Qualified_For_eSeal"; and 3) the processing shall stop the process. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 46 4.9 EU qualified electronic registered delivery service determination
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.9.1 Description
|
The procedure specified in clause 4.9 allows determining whether the signer identified in the certificate supporting the validation of the digital signature of a trust service output is confirmed by the applicable EUMS trusted list to have been, at a specific date and time, an EU qualified trust service provider for the provision of a qualified electronic registered delivery service. NOTE: The verification whether the trust service output is indeed a qualified electronic registered delivery service evidence or statement is out of scope of the present procedure.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.9.2 Inputs and parameters
|
Name Description of inputs CERT X.509 certificate for which the information is to be obtained (e.g. a ds:X509Certificate value of a ds:KeyInfo of the ds:Signature from the corresponding trust service output) Date-time A date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1].
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.9.3 Outputs
|
Name Description QERDSO-Results An indication of the EU qualified status of the QTSP/QTS identified through the subjectName attribute of CERT, which is one of the following values: a) "Not_Qualified" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to not have been, at Date-time, an EU qualified trust service provider for the provision of a qualified electronic registered delivery service; b) "Qualified" to indicate that the signer identified in the CERT is confirmed by the applicable EUMS trusted list from CC to have been, at Date-time, an EU qualified trust service provider for the provision of a qualified electronic registered delivery service; c) "Indeterminate" to indicate that the EUMS trusted list from CC cannot be used to confirm that the signer identified in the CERT has been, at Date-time, an EU qualified trust service provider for the provision of a qualified electronic registered delivery service. QERDSO-Status The status indication of the process. QERDSO-Sub-Status A list of indications supplementing QERDSO-Status indication. CC The country code of the EUMS trusted list being used to obtain the above listed three other outputs. OUT-4.9.3-01: All above listed output variables shall be initialized to void.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.9.4 Processing
|
PRO-4.9.4-01: If Date-time is before "2016-06-30T22:00:00Z", then: a) the processing shall set QERDSO-Status to the value "PROCESS_PASSED"; b) the processing shall set QERDSO-Results to the value "Not_Qualified"; and c) the processing shall stop the process. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 47 PRO-4.9.4-02: The processing shall set CC to the country code value of the countryName attribute of the subjectName field of the certificate provided in CERT, in capital letters in accordance with the ISO 3166-1 [2] Alpha 2 country code, with, when applicable: a) the country code value "GB" being converted to "UK"; b) the country code value "GR" being converted to "EL". PRO-4.9.4-03: The processing shall set TLS-Sti-1 to the value "http://uri.etsi.org/TrstSvc/Svctype/EDS/Q" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.9.4-04: The processing shall set TLS-Sti-2 to the value "http://uri.etsi.org/TrstSvc/Svctype/EDS/REM/Q" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.9.4-05: The processing shall run the process described in clause 4.3 of the present document, passing the following inputs to the process: a) CERT; b) TLS-Sti-1; c) Date-time; d) CC. PRO-4.9.4-06: The processing shall run the process described in clause 4.3 of the present document, passing the following inputs to the process: a) CERT; b) TLS-Sti-2; c) Date-time; d) CC. PRO-4.9.4-07: If both outputs SI-Status of the processes run in PRO-4.9.4-05 and in PRO-4.9.4-06 have the value "PROCESS_FAILED", then: a) the processing shall set QERDSO-Status to the value "PROCESS_FAILED"; b) the processing shall set QERDSO-Results to the value "Indeterminate"; c) the processing shall set QERDSO-Sub-Status to the set of values from SI-Status and SI-Sub-Status of both processes; and d) the processing shall stop the process. PRO-4.9.4-08: If both outputs SI-Results of the processes run in PRO-4.9.4-05 and in PRO-4.9.4-06 are void, then: a) the processing shall set QERDSO-Status to the value "PROCESS_PASSED"; b) the processing shall set QERDSO-Results to the value "Not_Qualified"; and c) the processing shall stop the process. PRO-4.9.4-09: If one of the outputs SI-Results of the processes run in PRO-4.9.4-05 and in PRO-4.9.4-06 includes more than one tuple for which the SI-at-Date-time respective parts include different values for their 'Service current status' or 'Service previous status' field, then: a) the processing shall set QERDSO-Status to the value "PROCESS_FAILED"; b) the processing shall set QERDSO-Results to the value "Indeterminate"; c) the processing shall set QERDSO-Sub-Status to the value "ERROR_INCONSISTENCY_IN_TL_ON_ERDS_CERT_STATUS"; and ETSI ETSI TS 119 615 V1.2.1 (2023-06) 48 d) the processing shall stop the process. PRO-4.9.4-10: If one of the outputs SI-Results of the processes run in PRO-4.9.4-05 and in PRO-4.9.4-06 includes more than one tuple for which the SI-at-Date-time respective parts include different public key values for their 'Service digital identifier' field (see clause 5.5.3 of ETSI TS 119 612 [1]), then the processing shall add to QERDSO-Sub-Status the value "WARNING_DUPLICATION_OF_SERVICE_INFORMATION_IN_TL_REGARDING_ERDS_CERT". PRO-4.9.4-11: When the SI-Results tuples from the processes run in PRO-4.9.4-05 and in PRO-4.9.4-06 include different TSP-Name values, then: a) the processing shall add to QERDSO-Sub-Status the indication value "ERROR_TSP_CONFLICT"; b) the processing shall set QERDSO-Results to the value "Indeterminate"; c) the processing shall set QERDSO-Status to the value "PROCESS_FAILED"; and d) the processing shall stop the process. PRO-4.9.4-12: If the organizationName attribute of the subjectName field of the certificate provided in CERT is not matching one of the values of TSP-Name or TSP-Trade-Name of all not void tuples from all tuples from output SI-Results of the processes run in PRO-4.9.4-05 and in PRO-4.9.4-06, then: a) the processing shall set QERDSO-Status to the value "PROCESS_FAILED"; b) the processing shall set QERDSO-Results to the value "Indeterminate"; c) the processing shall add to QERDSO-Sub-Status the value "ERROR_TSP_NAME_INCONSISTENCY_BETWEEN_ERDS_CERT_AND_TL"; and d) the processing shall stop the process. PRO-4.9.4-13: If the 'Service current status' or 'Service previous status' field(s) of the SI-at-Date-time part(s) of the output(s) SI-Results of any of the processes run in PRO-4.9.4-05 and in PRO-4.9.4-06 has (have) the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted": a) then: 1) the processing shall set QERDSO-Status to the value "PROCESS_PASSED"; 2) the processing shall set QERDSO-Results to the value "Qualified"; and 3) the processing shall stop the process. b) else: 1) the processing shall set QERDSO-Status to the value "PROCESS_PASSED"; 2) the processing shall set QERDSO-Results to the value "Not_Qualified"; and 3) the processing shall stop the process. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 49 Annex A (informative): Bibliography CEF eSignature - eIDAS Technical Subgroup and web conference on eSignature: "Reaching relying parties after a change of LOTL Administrative Anchors". ETSI ETSI TS 119 615 V1.2.1 (2023-06) 50 Annex B (informative): Change history Date Version Information about changes May 2021 1.1.1 Publication May 2023 1.2.1 CR#1 Fix of trust anchor usage when obtaining listed services matching a certificate CR#2 Fix of qualification determination of pre-eIDAS certificates at post-eIDAS times CR#3 Fix of pre-eIDAS status at post-eIDAS times CR#4 Fix of conflicting information between 'additionalServiceInformation' and 'Qualification' extensions CR#5 Fix of unexpected qualifiers for S/QSCDs CR#6 Fix of timestamp qualification determination CR#7 Fix wording on RFC 5280 processing CR#8 Fix normative requirement in note ETSI ETSI TS 119 615 V1.2.1 (2023-06) 51 History Document history V1.1.1 May 2021 Publication V1.2.1 June 2023 Publication
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
1 Scope
|
The present document specifies protocols and interfaces applicable when the process of creating AdES digital signatures as defined by ETSI TS 119 102-1 [i.7] and/or digital signature values, as result of Data To Be Signed Representations signatures, is carried out by a distributed solution comprised of two or more systems/services/components. The present document is limited to remote server signing, i.e. the signing key is held in a remote shared service. NOTE: Remote signature creation with local signing, i.e. the signing key is held with the signer's personal device but other steps in the signature creation are carried out by means of networked services, is a possible solution but protocols for such architecture are not covered in the present document. Finally, the present document specifies two bindings, each one in a different syntax (XML and JSON), for each of the protocols mentioned above. As far as it has been possible and suitable, the protocols have re-used constructs of CSC JSON and OASIS DSS-X XML specifications. When this has not been possible the present document specifies new components semantically and also syntactically in the two formats: XML and JSON. The authorized signer's use of its key for signing requires users to provide multiple proofs of their claimed identity before being granted access to the needed set of resources. The way in which the user identity verification process is carried out by the service provider or any suggestion concerning the usage of multi-factor authentication mechanisms is out of the scope of the present document.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
2 References
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] Cloud Signature Consortium Standard (Version 1.0.3.0): "Architectures and protocols for remote signature applications". NOTE: Available at https://cloudsignatureconsortium.org/wp- content/uploads/2019/02/CSC_API_V1_1.0.3.0.pdf. [2] OASIS Standard: "Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0", Committee Specification 02. NOTE: Available at https://docs.oasis-open.org/dss-x/dss-core/v2.0/cs02/dss-core-v2.0-cs02.zip. [3] OASIS Standard: "Advanced Electronic Signature Profiles of the OASIS Digital Signature Service Version 2.0", Working Draft 02. NOTE: Available at https://www.oasis-open.org/committees/download.php/63125/oasis-dssx-2.0-profiles- ades%20WD%2002.docx. [4] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". ETSI ETSI TS 119 432 V1.2.1 (2020-10) 9 [5] OASIS Standard: "Asynchronous Processing Abstract Profile of the OASIS Digital Signature Services Version 1.0". NOTE: Available at https://docs.oasis-open.org/dss/v1.0/oasis-dss-profiles-asynchronous_processing-spec-cs- v1.0-r1.pdf. [6] EN 419 241-1: "Trustworthy Systems Supporting Server Signing - Part 1: General System Security Requirements" (produced by CEN). [7] IETF RFC 5646: "Tags for Identifying Languages". [8] IETF RFC 4514: "Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names". [9] IETF RFC 3061: "A URN Namespace of Objects Identifiers". [10] IETF RFC 7468: "Textual Encodings of PKIX, PKCS, and CMS Structures". [11] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [12] ETSI EN 319 132-1: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures". [13] ETSI EN 319 142-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures". [14] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes".
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. [i.2] EN 419 221-5: "Protection profiles for TSP Cryptographic modules - Part 5: Cryptographic Module for Trust Services" (produced by CEN). [i.3] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.4] ETSI TS 119 312: "Electronic Signatures and Infrastructures (ESI); Cryptographic Suites". [i.5] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". [i.6] IETF RFC 7519: "JSON Web Token (JWT)". [i.7] ETSI TS 119 102-1 (V1.2.1): "Electronic signatures and infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation". [i.8] IETF RFC 8017: "PKCS #1: RSA Cryptography Specifications Version 2.2". [i.9] ETSI TS 103 173: "Electronic Signatures and Infrastructures (ESI); CAdES Baseline Profile". ETSI ETSI TS 119 432 V1.2.1 (2020-10) 10 [i.10] ETSI TS 103 171: "Electronic Signatures and Infrastructures (ESI); XAdES Baseline Profile". [i.11] ETSI TS 103 172: " Electronic Signatures and Infrastructures (ESI); PAdES Baseline Profile". [i.12] ETSI TS 119 431-1: "Electronic signatures and infrastructures (ESI); Policy and security requirements for trust service providers; Part 1: TSP service components operating a remote QSCD / SCDev". [i.13] ETSI TS 119 431-2: "Electronic signatures and infrastructures (ESI); Policy and security requirements for trust service providers; Part 2: TSP service components supporting AdES digital signature creation".
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
3 Definition of terms, symbols and abbreviations
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TR 119 001 [i.3] and the following apply: AdES (digital) signature: digital signature that is either a CAdES signature, or a PAdES signature or a XAdES signature client application: application running in a signer's environment that accesses the services made available by the SCASC and/or the SSASC digital signature: data appended to, or a cryptographic transformation of a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery (e.g. by the recipient) digital signature value: result of the cryptographic transformation of a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery (e.g. by the recipient) remote signature creation device: signature creation device used remotely from signer perspective and providing control of signing operation on the signer's behalf server signing application: application using a remote signature creation device to create a digital signature value on behalf of a signer server signing application service component: TSP service component employing a server signing application server signing application service provider: TSP operating a server signing application service component signature creation application: application within the signature creation system that creates the AdES digital signature and relies on the SCDev to create a digital signature value NOTE: The SCDev can be managed by the SSASC. signature creation application service component: TSP service component employing a signature creation application signature creation application service provider: TSP operating a signature creation application service component signature creation constraint: criteria used when creating a digital signature signature creation device: configured software or hardware used to implement the signature creation data and to create a digital signature value signature creation policy: set of signature creation constraints processed or to be processed by the SCASC or the SSASC signature creation service: TSP service implementing a signature creation application and/or a server signing application ETSI ETSI TS 119 432 V1.2.1 (2020-10) 11 signature creation service provider: service provider offering a signature creation service NOTE: As defined in CEN EN 419 241-1 [6]. signature credential: set of the signing key and the corresponding signing certificate
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
3.2 Symbols
|
Void.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: API Application Program Interface ASN Abstract Syntax Notation CA Certification Authority CEN European Committee for Standardization CRL Certificate Revocation List CSC Cloud Signature Consortium DSS-X Digital Signature Services eXtended DSV Digital Signature Value DTBS Data To Be Signed DTBSF Data To Be Signed Formatted DTBSR Data To Be Signed Representation ECDSA Elliptic Curve Digital Signature Algorithm EN European Norm HTTP Hyper Text Transfer Protocol ISO International Organization for Standardization JPEG Joint Photographic Experts Group JSON Java Script Object Notation JWT JSON Web Token LT Long Term LTA Long Term Archival OASIS Organization for the Advancement of Structured Information Standards OCSP Online Certificate Status Protocol OID Object IDentifier PNG Portable Network Graphics QES Qualified Electronic Signature QSCD Qualified electronic Signature Creation Device RA Registration Authority RSA Rivest, Shamir, & Adleman SAD Signature Activation Data SAM Signature Activation Module SAML Security Access Markup Language SCA Signature Creation Application SCAL Sole Control Assurance Level SCAL1 Sole Control Assurance Level 1 NOTE: As defined in CEN EN 419 241-1 [6]. SCAL2 Sole Control Assurance Level 2 NOTE: As defined in CEN EN 419 241-1 [6]. SCASC Signature Creation Application Service Component SCDev Signature Creation Device SCS Signature Creation Service SCSP Signature Creation Service Provider SD Signer's Document SDO Signed Data Object ETSI ETSI TS 119 432 V1.2.1 (2020-10) 12 SDOC Signed Data Object Composer SDR Signer's Document Representation SSA Server Signing Application SSASC Server Signing Application Service Component TSP Trust Service Provider URI Uniform Resource Identifier URL Uniform Resource Locator URN Uniform Resource Name XML eXtended Markup Language XSD XML Schema Definition
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4 Signature creation process, service decomposition
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.1 Signature creation process steps and data elements
|
Figure 1 (derived from ETSI TS 119 102-1 [i.7], clause 4.2.1) shows the various steps and the related data elements for a signature creation process. For remote signature creation, different steps of this process are carried out according to a decomposition into several components, which will have access to or make available the corresponding data elements. The process illustrated in the figure below is limited to the buildings blocks and information needed for creating a signature without taking in consideration issues such as signer authentication, authorization to the signing key usage or signing certificate availability. The signature activation module in the tamper protected area is needed only when the Signature Creation Service (SCS) complies to the Sole Control Assurance Level 2 (SCAL2) signature activation mechanism. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 13 Figure 1: Process Steps and Data Elements in Signature Creation
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.2 Service main components and interfaces
|
The above process points out scenarios where the AdES and/or Digital Signature Value (DSV) are created using a signing key held within a cryptographic security module named Signature Creation Device (SCDev) operated by a Signature Creation Service Provider (SCSP). Based on the different types of data managed in requests and responses, two main components can be identified in the above schema providing different interfaces for signing management: the Server Signing Application Service Component (SSASC) and the Signature Creation Application Service Component (SCASC) defined below. The SSASC is the component supporting digital signature values creation. The SSASC is able to interact with the SCDev holding the signer's private key. When the SSASC uses the SCDev, the authorized signer is able to control the signing key with a certain level of confidence. The SSASC interface has the Data To Be Signed Representation (DTBSR) and other parameters as main input and the digital signature value as main output. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 14 The SCASC is the component supporting AdES digital signature creation and carrying out several specific parts of the signature creation process. The SCASC is able to interact with the SSASC for requesting digital signature values creation. The SCASC interface has the document(s) to be signed (SD) or its (their) representation (SDR) and other parameters as main input and the signed document(s) or the digital signature(s) as main output. SCS denotes a TSP service implementing a Signature Creation Application (SCA) and/or a Server Signing Application (SSA). Some variants of these interfaces are possible depending on the functional split between the SCS and the signer's local system. The following clauses specify main information objects and processes in SCASC and SSASC.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.3 Signature Creation Application
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.3.1 Signer's document and hashing
|
The signature creation process starts with the signer's document (SD), which is to be signed. The SD is represented (SDR) by a hash value in the Data To Be Signed (DTBS). The following observations are made: • The creation of the SDR (the hashing) can be done where the SD is stored or by the SCASC. In the former case, the SDR is transferred to the SCASC while in the latter case, the SD is transferred to the SCASC. • The SD is part of the final Signed Data Object (SDO). Part of the Signed Data Object Composer (SDOC) function (building of the final AdES format) is to relate the digital signature value to the SD. An important design decision for remote signature creation services is where the SD, and thus its content, needs to be available. Making available only the SDR limits threats to confidentiality but may result in limitations in the functionality of the remote signature creation solution (i.e. when enveloping or enveloped signatures need to be created, or when visual representation of the signature needs to be included).
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.3.2 DTBS composition and formatting
|
In the two processes of DTBS composition and formatting, which in the context of the present document are seen together, the SDR (hash of the document to be signed) and hashes of all signed attributes are assembled into the Data To Be Signed Formatted (DTBSF). In addition to a certificate identifier (hash of signing certificate, possibly also of further certificates in a certificate chain) as indicated in the figure, further signed attributes are required or allowed by the ETSI standard signature formats (C/X/PAdES). For example all baseline CAdES and XAdES variants require the presence of the signed attributes "document type" (of SD) and "claimed signing time". The signed attributes or their hash values, whose presence is needed in the DTBS, are available to the SCASC when the DTBSF is created by the SCASC.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.3.3 DTBS preparation
|
This step consists of creating the DTBSR from the DTBSF. The SCASC prepares the entire DTBSF, calculates the hash, and sends the hash value (DTBSR) as input to an SSASC.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.3.4 SDO composer
|
As the final step, the SDO (the AdES format) is constructed. This consists of combining the digital signature value with other parameters into the requested format. Depending on the format, the digital signature made available for the SD is named: • Enveloped: The signature is added to the SD (e.g. PAdES signature). • Enveloping: The signature wraps the SD (e.g. certain CAdES formats). • Detached: The signature is a separate object linked to the SD. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 15 The SDO composing is done by a separate service instance or integrated with other functions in the SCASC.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.4 Server Signing Application
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.4.1 Signature creation
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.4.1.1 Introduction
|
The purpose of the signature creation process is to take the DTBSR and create a digital signature value under the control of the signer. In the context of the present document, the creation of the digital signature value is managed by an SSASC that uses a signing key, held within a cryptographic security module (SCDev), that the signers can activate by means of a secure authorization and activation process.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.4.1.2 Signature activation
|
The SSASC uses a remote SCDev in order to generate, maintain and use the signing keys under the control of their authorized signers. The authorized signer remotely controls the signing key with a certain level of confidence eventually by means of the Signature Activation Module (SAM). The SAM is a software component using the Signature Activation Data (SAD) to authenticate the signer and gain its authorization to activate its signing key for the purpose of signing the DTBSR. This process ensures confidence that the signing keys are under the control of the signer. Two different levels of confidence of the control of the signing key, as defined in CEN EN 419241-1 [6], are considered in the present document: • Sole Control Assurance Level 1 (SCAL1): - The signing keys are used, with a low level of confidence, under the sole control of the signer. - The authorized signer's use of its key for signing is enforced by the SSASC which authenticates the signer. The activation of the signing key can remain for a given period and/or for a given number of signatures. NOTE: It is not expected that such implementations would meet the requirements of sole control as it would be expected for a stand-alone QSCD as defined in the eIDAS [i.1] Regulation. • Sole Control Assurance Level 2 (SCAL2): - The signing keys are used, with a high level of confidence, under the sole control of the signer. - The authorized signer's use of its key for signing is enforced by the signature activation module by means of signature activation data provided, by the signer, using a signature activation protocol, in order to enable the use of the corresponding signing key to sign specific documents.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
4.4.1.3 Signature creation by SCDev
|
The signature creation process is performed by the SCDev. In the context of the present document, only architectures where the signature creation process is carried out by a remote SCDev are considered. According to the above sole control assurance levels the signing key can be used to generate the digital signature value creation after a successful signer authentication by the SSASC (SCAL1) or after a successful SAD verification by the SAM. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 16
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
5 Architectures for server signing
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
5.1 Overview
|
This clause describes the architectures of systems supporting remote server signing pointing out the fundamental interactions of SCASC and SSASC with the other parties involved in remote signature processes and taking in consideration the level of confidence of the control of the signing keys. A typical schema for representing systems supporting remote server signing (providing QES and/or AdES) includes a SCASC that is connected to a SSASC hosting the remote SCDev. Services such as CA/RA, OCSP and CRLs, timestamping and authentication and/or authorization servers are considered external to the schema. Two main scenarios are considered: • the signature client application sends to the signature creation service provider requests to generate one or more AdESs; • the signature client application sends to the signature creation service provider requests to generate one or more digital signature values and then completes the creation of the AdES structure. The defined protocols allow both SCASC and SSASC to implement batch signing for documents, hashes of documents and DTBSRs. In such processes of batch signatures of documents the signer is not requested to explicitly approve each document signature.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
5.2 Introduction to architectures
|
Two different architectures are presented in the following clauses in which SCASC and SSASC implement different authentication and authorization mechanisms according to the level of confidence of the control of the signing keys, taking in consideration that the TSP managing SCASC and/or SSASC can delegate the authentication and authorization processes to an external party (e.g. to an identity and/or an authentication provider). The architectures include two main environments: the signer's environment and the TSP protected environment. NOTE: In case of an SCS complying to SCAL2, the TSP protected environment includes a tamper protected device (e.g. cryptographic module conforming to CEN EN 419 221-5 [i.2]). The signer's environment is local to the signer and its protection is under the responsibility of the signer. The TSP protected environment is operated according to the security policy chosen by the TSP for securing the operations of the SCS and can store in a protected form, signing key(s) and link(s) between key(s) and signer(s). In the following models the dotted lines are used to represent data streams that are not part of the protocols defined in the present document and are shown only for the purpose of specifying any possible features of the illustrated services.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
5.3 Remote signing services with SCAL1
|
In this model the signing key's confidentiality and integrity are ensured by the SCDev that can be activated by the SSASC. Such activation can remain for a given period and/or for a given number of signatures. The signer can be authenticated by an SCASC or an SSASC depending on whether the SCSP is hosting an SCASC and/or an SSASC. If the SCSP is hosting only the SSASC then the SCASC can be provided i.e. directly in the signer environment or by a different SCSP. SCASC and SSASC can delegate the signer authentication to an external party. When the signer authentication succeeds, the corresponding signing key may be used for signature operations on behalf of the signer within a certain time frame and/or a certain amount of signature operations thus allowing the management of bulk/batch signature operations. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 17 Figure 2 ETSI ETSI TS 119 432 V1.2.1 (2020-10) 18
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
5.4 Remote signing services with SCAL2
|
In this model a third main environment is defined in addition to the signer's and the TSP's protected environments: the tamper protected environment. It is operated within the TSP protected environment, protects the use of signing keys and enforces signature activation to be under the signer control with a greater degree of confidence than in the previous model. In this model, the signing key confidentiality and integrity are ensured by the SAM that can be activated by the SSASC. The SAM verifies the SAD in order to be able to authorize the requested signature operation. The SAM can delegate signer authentication to an external party. When the SAD validation succeeds, the corresponding signing key may be used for signature operations on behalf of the signer. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 19 Figure 3 ETSI ETSI TS 119 432 V1.2.1 (2020-10) 20
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
5.5 Security, integrity and confidentiality
|
ETSI TS 119 431-2 [i.13] provides requirements for TSPs operating an SCASC supporting AdES digital signature creation. ETSI TS 119 431-1 [i.12] provides requirements for TSPs operating an SSASC supporting digital signature value creation.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
6 Protocol profiles specification
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
6.1 Introduction
|
The present document specifies the protocols semantics for requesting the digital signatures creation to a remote server and for receiving the related response. For the semantics mentioned above the present document specifies two bindings, each one in a different format (XML and JSON). As far as it has been possible and suitable, the profiles specified in the present document have taken as starting point a number of OASIS DSS-X Technical Committees' specifications, namely OASIS DSS-v2.0 [2], OASIS AdES profiles for DSS-v2.0 [3] and the CSC standard [1]. The rest of the present document is organized as follows: • Clauses 6.2 and 6.3 provide general remarks on the XML and JSON protocols. • Clause 7 specifies the components of the protocols for remote digital signature creation (XML and JSON) used by SSASC and SCASC. • Clause 8 specifies the messages that client applications and SCSs can exchange by using the components defined in clause 7. For each component of the protocols mentioned above, the present document: • Defines requirements for the semantics of the component (i.e. its mandatory contents, its optional contents, etc.). These requirements are defined in clauses "Component semantics". • Defines requirements for the XML component. These requirements are defined in clauses named "XML related component". • Defines requirements for the JSON. These requirements are defined in clauses named "JSON related component".
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
6.2 OASIS DSS-X XML related protocol
|
The structures described in the present document are contained in the schema files [DSS_Core_XSD], [XMLDSIG_XSD] and the four xml schema files equally identified with [XSDSIGCREATIONPROT] throughout the present document and whose location is defined in annex A. The new elements and types defined in that schema are defined within the XML namespace whose URI value is: http://uri.etsi.org/19432/v1.1.1#. Table 1 shows the URI values of other XML namespaces and their corresponding prefixes used in the schema files mentioned above and within the present document. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 21 Table 1 URI value of the XML Namespace Prefix http://uri.etsi.org/19432/v1.1.1# etsisig http://www.w3.org/2000/09/xmldsig# ds http://docs.oasis-open.org/dss-x/ns/base dsb http://docs.oasis-open.org/dss-x/ns/core dss2 The present document references components in the schema files mentioned above and further profiles some of them. In the absence of any further requirement defined in the present document, the requirements defined in the schema files mentioned above for each element present in the present document shall apply. In addition the present document specifies elements that are not specified in the schema files mentioned above. For these elements, the present document also defines the processing model for the server. This processing model is specified below the indication Processing model within each clause that specifies one of these elements.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
6.3 CSC JSON related protocol
|
The structures described in the present document are contained in the schema files [ETSI_SIG_CORE_JSCHEMA]. In addition, the present document specifies elements that are not specified in the CSC standard [1]. For these elements the present document also defines the processing model for the server. This processing model is specified below the indication Processing model within each clause that specifies one of these elements.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7 Protocol components definitions
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.1 Introduction
|
Clause 7 defines the protocol components for remote digital signature creation. The components represent the data that can be passed to or returned by the SCS in order to request and execute the SCS functionalities. Clause 8 defines the profiles implemented by the SCS that make use of the components defined in this clause. 7.2 Component for asynchronous/synchronous operation mode selection
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.2.1 Component semantics
|
The term synchronous operation mode means that the client application, after sending any request to the SCS, will wait for it to finish before moving on to another task. In this operation mode the SCS will perform the requested operation and return the corresponding outcome(s) to the client application. The term asynchronous operation mode means that the client application, after sending any request to the SCS, can move on to another task before the requested operation finishes. In this operation mode the SCS will accept the request and return a notification informing the client application about the acceptance of its request. The client will be able to request the corresponding outcome(s) to the SCS later on. This component shall be used by a client application to request a synchronous or asynchronous operation mode from the SCS. NOTE 1: When this component is not specified by the client application, the SCS may take one of the following behaviours to perform the requested operation, according to the selected service policy: process the request only in synchronous mode; process the request only in asynchronous mode; process the request in synchronous mode and decide under particular conditions to process the request in asynchronous mode. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 22 NOTE 2: When the asynchronous processing is initiated by the SCS it returns a response including: a result code informing the client application about the requested operation processing in asynchronous mode (see clause 7.24); and a unique response identifier that the client application will use to obtain the outcome(s) of the requested operation from the SCS (see clause 7.26). Details on the asynchronous processing mode are described in clause 8.4.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.2.2 JSON related component
|
The component for requesting the operation mode selection shall be represented by the following: • operationMode string type parameter. Specified according to table 2. Table 2 Parameter Type Description operationMode String The type of operation mode requested to the SCS. It shall take one of the following values: • "A": an asynchronous operation mode is requested. • "S": a synchronous operation mode is requested.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.2.3 XML related component
|
The element for asynchronous/synchronous operation mode selection shall be etsisig:OperationMode, child element of the dss2:OptionalInputs element. The OperationMode element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2, and is copied below for information: <xs:element name="OperationMode" type="etsisig:OperationModeType" /> <xs:simpleType name="OperationModeType"> <xs:restriction base="xs:string"> <xs:enumeration value="Synchronous" /> <xs:enumeration value="Asynchronous" /> </xs:restriction> </xs:simpleType>
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.2.4 Processing model
|
When this component is not provided by the client application, the SCS shall take one of the following behaviours to perform the requested operation, according to the selected service policy: • process the request only in synchronous mode; or • process the request only in asynchronous mode; or • process the request in synchronous mode and decide under particular conditions to process the request in asynchronous mode. When the synchronous processing is adopted by the SCS it shall return: • the response defined in clause 8.2.2 in case of AdES signatures creation requests; • the response defined in clause 8.3.2 in case of DSVs creation requests. When the asynchronous processing is adopted by the SCS it shall return an initial response including: • a result code informing the client application about the requested operation processing in asynchronous mode (see clause 7.24); and ETSI ETSI TS 119 432 V1.2.1 (2020-10) 23 • a unique response identifier that the client application will use to obtain the outcome(s) of the requested operation from the SCS (see clause 7.26). The asynchronous processing mode is defined in clause 8.4.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.3 Component for identification of the request
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.3.1 Component semantics
|
This component contains a string value included by the client application and is used to correlate requests with subsequent corresponding responses or to poll asynchronous requests outcome(s).
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.3.2 JSON related component
|
The component for the identification of the request shall be represented by the following: • requestID string type parameter. Specified according to table 3. Table 3 Parameter Type Description requestID String Data from the client application generally used to handle a signature transaction identifier.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.3.3 XML related component
|
The element for correlating requests with subsequent responses shall be the RequestID attribute of the dss2:SignRequest root element and the RequestId attribute of the dss2:SignResponse root element defined in OASIS DSS-v2.0 [2], clause 4.4.1.2.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.4 Component for credential authorization
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.4.1 Component semantics
|
This component shall contain the information needed to authorize the use of the signing key. When the Sole Control Assurance Level 1 (SCAL1) is implemented, this component contains the data used to control, with a low level of confidence, that a given signature operation is performed on behalf of the signer under sole control of the signer. When the Sole Control Assurance Level 2 (SCAL2) is implemented, this component contains the data used to control, with a high level of confidence, that a given signature operation is performed on behalf of the signer under sole control of the signer.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.4.2 JSON related component
|
The component for submitting the credential authorization shall be represented by the following: • SAD string type parameter. Specified according to table 4. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 24 Table 4 Parameter Type Description SAD String Authentication data used to authorize the use of the signing key. The "SAD" element is defined in clause 11.6 of the CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.4.3 XML related component
|
The element for credential authorization shall be etsisig:SignatureActivationData, child element of the dss2:OptionalInputs element. If the value to be submitted is not of string type, it shall be encoded into a string value using Base64 encoding. The SignatureActivationData element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2, and is copied below for information: <xs:element name="SignatureActivationData" type="etsisig:SignatureActivationDataType" /> <xs:complexType name="SignatureActivationDataType"> <xs:simpleContent> <xs:extension base="xs:string"> <xs:attribute name="type" type="xs:string" use="optional" /> </xs:extension> </xs:simpleContent> </xs:complexType>
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.5 Component for defining optional data to be returned
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.5.1 Component semantics
|
This component defines a set of additional outputs associated with the processing of a signature or certificate information retrieval request and shall be used by the client application to define optional data to be returned from the SCS. This element shall contain a list of element names of the optional data requested. Below follows a list of the sub-components that constitute this component: • The optional returnSigningCertificateInfo element, if present, shall contain a Boolean. Its default value is 'false'. This element can be used by the client application to obtain various information concerning the signing certificate/chain/key used by the SCS to perform the signature or identified in the certificate information retrieval request. • The component defined in clause 7.10 shall be used in order to specify to the SCS which information concerning the signing certificate/chain/key shall be returned. • The optional returnSupportMultiSignatureInfo element, if present, shall contain a Boolean. Its default value is 'false'. This element can be used by the client application to obtain the information whether the signing key supports the creation of multiple signatures with a single authorization request. • The optional returnServicePolicyInfo element, if present, shall contain a Boolean. Its default value is 'false'. This element can be used by the client application to obtain the name of the service policy used by the server to perform the requested operation. • The optional returnSignatureCreationPolicyInfo element, if present, shall contain a Boolean. Its default value is 'false'. This element can be used by the client application to obtain the name of the signature creation policy used by the server to perform the requested signature creation operation. • The optional returnCredentialAuthorizationModeInfo element, if present, shall contain a Boolean. Its default value is 'false'. This element can be used by the client application to obtain the authorization mode required by the signing key identified in the certificate information retrieval request. • The optional returnSoleControlAssuranceLevelInfo element, if present, shall contain a Boolean. Its default value is 'false'. This element can be used by the client application to obtain the sole control assurance level required by the signing key identified in the certificate information retrieval request. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 25
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.5.2 JSON related component
|
The component for specifying the optional data to be returned from the SCS shall be represented by the following parameters: • returnSigningCertificateInfo • returnSupportMultiSignatureInfo • returnServicePolicyInfo • returnSignatureCreationPolicyInfo • returnCredentialAuthorizationModeInfo • returnSoleControlAssuranceLevelInfo Specified according to table 5. Table 5 Parameter Presence Type returnSigningCertificateInfo Optional Boolean returnSupportMultiSignatureInfo Optional Boolean returnServicePolicyInfo Optional Boolean returnSignatureCreationPolicyInfo Optional Boolean returnCredentialAuthorizationModeInfo Optional Boolean returnSoleControlAssuranceLevelInfo Optional Boolean The "ReturnSigningCertificateInfo", "ReturnSupportMultiSignatureInfo", "ReturnServicePolicyInfo", "ReturnSignatureCreationPolicyInfo", "ReturnCredentialAuthorizationModeInfo" and "ReturnSoleControlAssuranceLevelInfo" elements are not defined in CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.5.3 XML related component
|
The element for requesting optional data to be returned shall be the optional element etsisig:ReturnOptionalData, contained in the dss2:OptionalInputs element. The ReturnOptionalData element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2, and is copied below for information: <xs:element name="ReturnOptionalData" type="etsisig:ReturnOptionalDataType"/> <xs:complexType name="ReturnOptionalDataType"> <xs:sequence> <xs:element ref="etsisig:SigningCertificateInfo" minOccurs="0"/> <xs:element ref="etsisig:SupportMultiSignatureInfo" minOccurs="0"/> <xs:element ref="etsisig:ServicePolicyInfo" minOccurs="0"/> <xs:element ref="etsisig:SignatureCreationPolicyInfo" minOccurs="0"/> <xs:element ref="etsisig:CredentialAuthorizationModeInfo" minOccurs="0"/> <xs:element ref="etsisig:SoleControlAssuranceLevelInfo" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:element name="SigningCertificateInfo" type="xs:Boolean"/> <xs:element name="SupportMultiSignatureInfo" type="xs:Boolean"/> <xs:element name="ServicePolicyInfo" type="xs:Boolean"/> <xs:element name="SignatureCreationPolicyInfo" type="xs:Boolean"/> <xs:element name="CredentialAuthorizationModeInfo" type="xs:Boolean"/> <xs:element name="SoleControlAssuranceLevelInfo" type="xs:Boolean"/>
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.5.4 Processing model
|
If the SCS does not recognize or cannot handle any optional data to be returned, it shall reject the request and return an error. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 26 7.6 Component for defining the validity period for asynchronous requests
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.6.1 Component semantics
|
This component shall be used to specify a maximum period of time until which the SCS shall keep the request outcome(s) available for the client application retrieval. The validity period shall be calculated starting from the moment of the request acceptance. The SCS needs not to return any outcome(s) after the maximum period of time expiration and may destroy any outcome(s) already produced.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.6.2 JSON related component
|
The component for requesting the maximum period of time setting shall be represented by the following: • validityPeriod number type parameter. Specified according to table 6. Table 6 Parameter Type Description validityPeriod Integer Maximum period of time expressed in milliseconds.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.6.3 XML related component
|
The element for defining the validity period for asynchronous requests shall be etsisig:ValidityPeriod, child element of the dss2:OptionalInputs element. The value specifies the maximum period of time, starting from the asynchronous request acceptance and expressed in milliseconds, within which the asynchronous request outcome(s) retrieval can be completed. The ValidityPeriod element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2, and is copied below for information: <xs:element name="ValidityPeriod" type="xs:int" />
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.6.4 Processing model
|
If the component is present, the SCS shall perform the requested operations and keep available the corresponding outcome(s) within the period of time specified in this component. If the SCS does not complete the requested operations or the client application does not request the available outcome(s) within the specified period of time, the processing of the client application request shall not be completed successfully.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.7 Component for the client application authentication
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.7.1 Component semantics
|
This component shall contain information to authenticate the client application to access to the SCASC or the SSASC. NOTE 1: The way a client application authenticates to the SCASC or SSASC is out of scope of the present document. NOTE 2: The SCSP can define other ways in which a client application can authenticate to the SCASC or SSASC in addition or alternatively to this component usage.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.7.2 JSON related component
|
The authorization component shall be included into the Authorization HTTP header of every call. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 27
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.7.3 XML related component
|
The element for the client application authentication shall be dss2:ClaimedIdentity, child element of the dss2:OptionalInputs element, defined in OASIS DSS-v2.0 [2], clause 4.4.9.2. The component semantics are defined as being the identification of the requesting service. The precise authentication mechanism (i.e. the usage of SupportingInfo, etc.) is out of scope for the present document and will be defined by the implementing service.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.8 Component for identifying signature credentials
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.8.1 Component semantics
|
This component is used to uniquely identify the signer's private key and corresponding certificate to be used for signature creation.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.8.2 JSON related component
|
The component for requesting the operation mode selection shall be represented by the following: • credentialID string type parameter. Specified according to table 7. Table 7 Parameter Type Description credentialID String The identifier associated to the private key and corresponding certificate. The "credentialID" element is defined in clause 11.6 of the CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.8.3 XML related component
|
The element for identifying signature credentials shall be the dss2:KeySelector, child element of dss2:OptionalInputs element, defined in OASIS DSS-v2.0 [2], clause 4.4.12.2. The contents of KeySelector shall be processed in the same way as it is specified in the document mentioned above.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.9 Component for language selection
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.9.1 Component semantics
|
This component shall be used to request a preferred language of the response and shall be specified according to IETF RFC 5646 [7]. The service should provide language-specific responses using the requested language. In the case the requested language is not supported then no error shall be raised and the responses shall be produced in the SCS default language.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.9.2 JSON related component
|
The component for selecting language and region settings shall be represented by the following: • lang string type parameter. Specified according to table 8. Table 8 Parameter Type Description Lang String requested response language specified as in IETF RFC 5646 [7]. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 28 The "Lang" element is defined in clause 11.1 of the CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.9.3 XML related component
|
The element for language and culture selection shall be dsb:Language, child element of the dss2:OptionalInputs element, defined in OASIS DSS-v2.0 [2], clause 4.2.8.2. 7.10 Component for specifying the contents from certificate info to be returned
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.10.1 Component semantics
|
This component is used to specify which contents of the signing certificate chain shall be returned. If this component is not defined the SCS shall return only the end-entity certificate.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.10.2 JSON related component
|
The component for specifying which contents of the certificate chain shall be returned by the SCS shall be represented by the following: • certificates string type parameter. • authInfo Boolean type parameter. • certInfo Boolean type parameter. Specified according to table 9. Table 9 Parameter Presence Type Description certificates Optional String Specifies which certificates from the certificates chain shall be returned in the SCS response: • "none": no certificate is returned. • "single": only the end entity certificate is returned. • "chain": the full certificate chain is returned. The default value is "single". certInfo Optional conditional Boolean Specifies if the information on the end entity certificate shall be returned as printable strings. The default value is "false", so if the parameter is omitted then the information will not be returned. This element shall carry a value only if the parameter certificates contains a value different from "none". authInfo Optional conditional Boolean Specifies if the information on the authorization mechanisms supported by this credential shall be returned. The default value is "false", so if the parameter is omitted then the information will not be returned. This element shall carry a value only if the parameter certificates contains a value different from "none". The "certificates", "certInfo" and "authInfo" elements are defined in clause 11.5 of the CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.10.3 XML related component
|
The element for listing the certificate chain shall be etsisig:ReturnSigningCertificate, child element of the etsisig:OptionalInputs element. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 29 The ReturnSigningCertificate element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2, and is copied below for information. <xs:element name="ReturnSigningCertificate" type="etsisig:ReturnSigningCertificateType" /> <xs:complexType name="ReturnSigningCertificateType"> <xs:attribute name="ReturnCertificates" type="etsisig:ReturnCertificatesType" use="optional" /> <xs:attribute name="CertificateInfo" type="xs:Boolean" use="optional" /> <xs:attribute name="AuthorizationInfo" type="xs:Boolean" use="optional" /> </xs:complexType> <xs:simpleType name="ReturnCertificatesType"> <xs:restriction base="xs:string"> <xs:enumeration value="None" /> <xs:enumeration value="Single" /> <xs:enumeration value="Chain" /> </xs:restriction> </xs:simpleType>
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.10.4 Processing model
|
If the component is present, the SCS shall check the values passed in the component parameters. If the parameter indicating which certificates shall be returned is present the SCS shall return in its response no certificate, only the signing certificate or the full signing certificate chain if the parameter value is respectively "none", "single" or "chain". If the parameter indicating if signing certificate information shall be returned in the form of strings is valued "true" the SCS shall return in its response the signing certificate information as specified in clause 7.22. If the parameter indicating if signing key and certificate authorization information shall be returned is valued "true" the SCS shall return in its response the signing key and certificate authorization information as specified in clause 7.28.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.11 Component for managing digital signatures transactions
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.11.1 Component semantics
|
This component may be used to initiate and manage a sequence of an agreed number of signatures to be regarded as a single unit of work (named transaction in the present clause) between the client and the SCS. The transaction shall be identified by the component defined in clause 7.3 that will be handled in order to create a transaction identifier uniquely within the SCS. EXAMPLE 1: A working transaction in which a signer needs to put in a document a certain number of PAdES signatures in different parts in order to acknowledge different contents in the document. In such a case, a new DTBS is computed before every new signature. Using a working transaction to complete all the signatures allows the signer to have a better control of the whole signature process. EXAMPLE 2: A signer is requesting to sign a very large number of documents, where each document is being included in the request in its entirety and each document is fairly big. This component can be used to prevent the request from being very big. Instead of sending all the documents to the SCASC at the same time, the documents can be sent one at a time, and they would be signed with the same signer action. The session key would be used to be sure that subsequent documents belong to the same transaction. NOTE: The definition of the authorization protocol is out of scope of the present document.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.11.2 JSON related component
|
The component for initiating and managing a transaction shall be represented by the following: • numSignatures integer parameter. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 30 Specified according to table 10. Table 10 Parameter Type Description numSignatures Integer The number of signatures to be performed in the context of the transaction. The SCS will check this value in the context of the transaction. The "numSignatures" element is defined in clause 11.6 of the CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.11.3 XML related component
|
The element for managing digital signature transaction shall be the etsisig:NumberOfSignatures element, child element of dss2:OptionalInputs. The etsisig:NumberOfSignatures element shall be defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2, and is copied below for information. <xs:element name="NumberOfSignatures" type="xs:int"/>
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.11.4 Processing model
|
If the component is present, the SCS shall check and store the value passed in the component parameter. The SCS response shall include a unique identifier in the component for the identification of response as defined in clause 7.26. Any further signature request that contains this unique identifier in the component for request identification, shall be considered being part of the signature transaction. The response to any signature request being part of the transaction shall include the same value in the component for response identification. After the SCS will have received the number of signature requests expected in the transaction any further requests including the same request identification value shall be refused by the SCS that shall return an unsuccessful response.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.12 Component for service policy selection
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.12.1 Component semantics
|
This component shall contain a non-ambiguous identifier of the service policy under which the server shall perform the requested operation.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.12.2 JSON related component
|
The component for specifying the identifier of the service policy under which the server shall perform the requested operation shall be represented by the following: • policy string type parameter. Specified according to table 11. Table 11 Parameter Type Description policy String The element that identifies a particular service policy associated with the SCS. The policy element may be used to select a specific service policy if a SCS supports multiple policies, or as a sanity-check to make sure the SCS implements the service policy the client expects.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.12.3 XML related component
|
The element for service policy selection shall be dsb:ServicePolicy, child element of the dss2:OptionalInputs element, defined in OASIS DSS-v2.0 [2], clause 4.2.8.2. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 31
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.13 Component for signature creation policy selection
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.13.1 Component semantics
|
This component shall contain the signature creation policy that shall be used while signing the DTBSR(s) and shall have the value of a unique identifier of the signature creation policy as an URI. If the identifier of the signature creation policy is an OID, then the value of this element shall be an URN indicating the value of the OID mentioned above as specified in IETF RFC 3061 [9]. Alternatively to an explicit identification of the signature creation policy the information specifying the signature algorithm to be used may be provided.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.13.2 JSON related component
|
The component for specifying the signature creation policy identification to be used by the SCS shall be represented by the following: • signaturePolicyID string type parameter;5 • signAlgo string type parameter; • signAlgoParams string type parameter. Specified according to table 12. Table 12 Parameter Presence Type Description signaturePolicyID Required Conditional String The element that identifies a particular signature creation policy associated with the SCS. This element shall carry a value if the signAlgo parameter is not specified. signAlgo Required Conditional String The element specifies the algorithm OID used for signing. This element shall carry a value if the signaturePolicyID parameter is not specified. signAlgoParams Optional Conditional String The element specifies the Base64-encoding of the DER-encoded ASN.1 signature parameters. This element may carry a value only if required and/or allowed by the signature algorithm like, for example, the RSA-PSS cryptographic signature scheme (IETF RFC 8017 [i.8]). The "signaturePolicyID" element is not defined in CSC standard [1]. The "signAlgo" and "signAlgoParams" elements are defined in clause 11.9 of the CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.13.3 XML related component
|
The element for signature algorithm selection shall be dss2:SignatureAlgorithm, child element of the dss2:OptionalInputsSign element, defined in OASIS DSS-v2.0 [2], clause 4.4.4.2. The element for signature policy selection shall be etsisig:SignaturePolicyId, child element of the dss2:OptionalInputs element. The element for signature algorithm parameters shall be etsisig:SignatureAlgorithmParameters, child element of the dss2:OptionalInputs element. The etsisig:SignaturePolicyId element shall be defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2, and is copied below for information. <xs:element name="SignaturePolicyId" type="xs:anyURI"/> The etsisig:SignatureAlgorithmParameters element shall be defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2, and is copied below for information. <xs:element name="SignatureAlgorithmParameters" type="xs:base64Binary"/> ETSI ETSI TS 119 432 V1.2.1 (2020-10) 32 7.14 Component for optional signature attributes/properties selection
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.14.1 Component semantics
|
The request may include this component if there are certain signed attributes/properties that the SCASC is requested to include in the signature. Below follows a list of the attributes/properties names that can be referenced in this component in order to request the inclusion of the corresponding signed attributes/properties in the signature. As an alternative to the attributes/properties names it is also possible using the corresponding attributes/properties oids: • The commitment-type-indication element, if present, shall contain the Base64-encoding of the attribute commitment-type-indication defined in clause 5.2.3 of ETSI EN 319 122-1 [11]. • The content-hints element, if present, shall contain the Base64-encoding of the attribute content-hints defined in clause 5.2.4.1 of ETSI EN 319 122-1 [11]. • The mime-type element, if present, shall contain the Base64-encoding of the attribute mime-type defined in clause 5.4.2.2 of ETSI EN 319 122-1 [11]. • The signer-location element, if present, shall contain the Base64-encoding of the attribute signer- location defined in clause 5.2.5 of ETSI EN 319 122-1 [11]. • The signer-attributes-v2 element, if present, shall contain the Base64-encoding of the attribute signer-attributes-v2 defined in clause 5.2.6.1 of ETSI EN 319 122-1 [11]. • The content-time-stamp element, if present, shall contain the Base64-encoding of the attribute content- time-stamp defined in clause 5.2.8 of ETSI EN 319 122-1 [11]. • The signature-policy-identifier element, if present, shall contain the Base64-encoding of the attribute signature-policy-identifier defined in clause 5.2.9 of ETSI EN 319 122-1 [11]. • The content-reference element, if present, shall contain the Base64-encoding of the attribute content- reference defined in clause 5.2.11 of ETSI EN 319 122-1 [11]. • The content-identifier element, if present, shall contain the Base64-encoding of the attribute content- identifier defined in clause 5.2.12 of ETSI EN 319 122-1 [11]. • The Location element, if present, shall contain the Base64-encoding of the attribute Location defined in clause 5.3 of ETSI EN 319 142-1 [13]. • The Reason element, if present, shall contain the Base64-encoding of the attribute Reason defined in clause 5.3 of ETSI EN 319 142-1 [13]. • The Name element, if present, shall contain the Base64-encoding of the attribute Name defined in clause 5.3 of ETSI EN 319 142-1 [13]. • The ContactInfo element, if present, shall contain the Base64-encoding of the attribute ContactInfo defined in clause 5.3 of ETSI EN 319 142-1 [13]. • The SignerRoleV2 element, if present, shall contain the Base64-encoding of the attribute SignerRoleV2 defined in clause 5.2.6 of ETSI EN 319 132-1 [12]. • The CommitmentTypeIndication element, if present, shall contain the Base64-encoding of the attribute CommitmentTypeIndication defined in clause 5.2.3 of ETSI EN 319 132-1 [12]. • The SignatureProductionPlaceV2 element, if present, shall contain the Base64-encoding of the attribute SignatureProductionPlaceV2 defined in clause 5.2.5 of ETSI EN 319 132-1 [12]. • The AllDataObjectsTimeStamp element, if present, shall contain the Base64-encoding of the attribute AllDataObjectsTimeStamp defined in clause 5.2.8.1 of ETSI EN 319 132-1 [12]. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 33 • The IndividualDataObjectsTimeStamp element, if present, shall contain the Base64-encoding of the attribute IndividualDataObjectsTimeStamp defined in clause 5.2.8.2 of ETSI EN 319 132-1 [12]. • The SignaturePolicyIdentifier element, if present, shall contain the Base64-encoding of the attribute SignaturePolicyIdentifier defined in clause 5.2.8.2 of ETSI EN 319 132-1 [12].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.14.2 JSON related component
|
The component for the selection of the attributes/properties to be included in the signature shall be represented by the following array: • signedProps containing the list of attributes to be added to the signatures' signed attributes. Specified according to table 13. Table 13 Parameter Type Description signedProps Array of Attribute Object List of signed attributes. The attributes that may be included depend on the signature format and the signature creation policy. The 'Attribute Object' is a JSON Object composed by the following attributes: • attribute_name string type parameter; • attribute_value array of string type parameter. Specified according to table 14. Table 14 Parameter Presence Type Description attribute_name Required String Name or OID of the attribute/property to be included in the signature. The attributes and/or properties names defined in clause 7.14.1 shall be used. Other attributes and/or properties whose names are defined in the table in clause 6.3 of ETSI EN 319 122-1 [11], ETSI EN 319 132-1 [12], ETSI EN 319 142-1 [13] documents may be supported by the SCS. attribute_value Conditional String Depending on the attribute/property specified in the attribute_name parameter, this parameter contains the value to be used for such attribute/property to be included in the signature. When some element of this parameter is not defined the SCASC shall calculate it, if needed.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.14.3 XML related component
|
The element for optional signature attributes/properties shall be dss2:Properties, child element to the dss2:OptionalInputs element, defined in OASIS DSS-v2.0 [2], clause 4.4.15.2.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.