hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4028be74228292868d82461bedfe5a9b | 119 615 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.4] and the following apply: EUMS European Union Member State LOTL List Of Trusted Lists LOTLSO LOTL Scheme Operator OJEU Official Journal of the European Union QTS Qualified Trust Service TL Trusted List TSP Trust Service Provider |
4028be74228292868d82461bedfe5a9b | 119 615 | 3.4 Notations | The requirements in the present document are identified as follows: <3 letters identifying the section title or type of requirement>-<the clause number>-<2-digit number (incremental)> The management of the requirement identifiers for subsequent editions of the present document is as follows: • When a requirement is ins... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.0 General provisions | The present document presents procedures for using and interpreting European Union Member States national trusted lists in the form of algorithms, which provide a conformant behaviour when implemented by a conformant application. GPR-4.0-01: Alternative implementations may be used provided that they shall produce the s... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.1 Authenticating the EC compiled list of trusted lists | |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.1.1 Description | EUMS Trusted Lists (TLs) have a legal constitutive value. It is the single formal source to verify that a claimed EU qualified trust service provider and the claimed EU qualified trust service it provides are indeed granted an EU qualified status by the competent EUMS body. Regulation (EU) No 910/2014 [i.1] mandates EU... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.1.2 Inputs | The parameters OJEU-Loc, OJEU-LOTL-Loc and OJEU-LOTL-Certs-Set shall either initially be configured as specified in GPR-4.0-02 or updated through the regular processing specified in clause 4.1.4. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.1.3 Outputs | Name Description Authenticated-LOTL The authenticated XML version of the current instance of the LOTL. LOTL-Status The status indication of the process of authenticating the current instance of the LOTL. LOTL-Sub-Status A list of indications supplementing LOTL-Status indication of the process of authenticating the curr... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.1.4 Processing | NOTE 1: The processing basically checks the chain of trust between the LOTL XML file obtained from OJEU-LOTL-Loc input and the OJEU-LOTL- Certs-Set input. It checks in particular that: - the public key certificate corresponding to the private key having signed the LOTL XML file is part of the set of certificates includ... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.2 Authenticating an EUMS trusted list | |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.2.1 Description | The procedure specified in clause 4.2 allows to obtain the authenticated XML version of the national TL of a given EUMS. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.2.2 Inputs | Name Description CC Country code of the EUMS for which the trusted list is to be authenticated and whose value is in accordance with the ISO 3166-1 [2] Alpha 2 country code, set in capital letters. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.2.3 Outputs | Name Description Authenticated-EUTL The authenticated XML version of the requested TL of EUMS CC. EUTL-Status The status indication of the process of authenticating the requested TL of EUMS CC. EUTL-Sub-Status A list of indications supplementing EUTL-Status indication of the process of authenticating the requested TL o... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.2.4 Processing | PRO-4.2.4-01: The processing shall run the process for authenticating the LOTL as described in clause 4.1 of the present document. PRO-4.2.4-02: If the output Authenticated-LOTL is void as a result of the execution of the process referred in PRO-4.2.4-01, then: a) the processing shall set EUTL-Status to the value "TL_V... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.3 Obtaining listed services matching a certificate | |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.3.1 Description | The procedure specified in clause 4.3 allows to obtain, from the trusted list of a specific country, matching listed services, associated service information for a certificate for a specific date and time, for a specific service type identifier. NOTE: The difference between a QTS type and a Service type identifier as s... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.3.2 Inputs | Name Description 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) TLS-Sti One of the Service type identifier URI values specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. Date-time Date and time indication as specified in clause 5.... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.3.3 Outputs | Name Description SI-Results A set of groups of elements, each group made of: a) SI-full defined as an XML section corresponding to a 'Service information' element as specified in clause 5.5 of ETSI TS 119 612 [1]; b) SI-at-Date-time defined as an XML section corresponding either to the Date-time related 'Service (curre... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.3.4 Processing | PRO-4.3.4-01: If CC represents an EUMS and/or is set to "GB" or "UK": a) then the processing shall run the process for authenticating the EUMS trusted list from CC as described in clause 4.2 of the present document, passing CC as input to the process; b) else: 1) the processing shall set SI-Status to the value "PROCESS... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.4 EU qualified certificate determination | |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.4.1 Description | The procedure specified in clause 4.4 allows determining whether a certificate is confirmed by the applicable EUMS trusted list to have been an EU qualified certificate at a specific date and time and for which type. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.4.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) Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1]. ETSI ETSI TS 119 615 V1.3.1 (2026-01) 20 |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.4.3 Outputs | Name Description QC-Results A set of indications of the EU qualified status of CERT through one or more of the following values: a) "Not_Qualified" to indicate that CERT is not an EU qualified certificate according to the EUMS trusted list from CC at Date-time; b) "Not_Qualified_For_eSig" to indicate that CERT is not a... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.4.4 Processing | PRO-4.4.4-01: The processing shall set CC to the country code value of the countryName attribute of the issuer 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 c... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.5 QSCD determination | |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.5.1 Description | The procedure specified in clause 4.5 allows determining whether an EU qualified certificate is confirmed by the applicable EUMS trusted list to have had its private key residing in a QSCD at a specific date and time. NOTE: As the EUMS trusted list provides such information only for qualified certificates of a certain ... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.5.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). Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1]. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.5.3 Outputs | Name Description QSCD-Results An indication on whether CERT had its private key residing in a QSCD in accordance with the trusted lists, through one of the following values: a) "QSCD_YES" to indicate that CERT had its private key residing in a QSCD at Date-time according to the EUMS trusted lists; b) "QSCD_NO" to indic... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.5.4 Processing | PRO-4.5.4-01: The processing shall run the process described in clause 4.4 of the present document, passing the following inputs to the process: a) CERT; b) Date-time. ETSI ETSI TS 119 615 V1.3.1 (2026-01) 35 PRO-4.5.4-02: If the output QC-Status of the process run in PRO-4.5.4-01 has the value "PROCESS_FAILED", then: ... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.6 EU trust service token issuer qualification determination | |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.6.1 Description | The procedure specified in the present clause 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 provide... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.6.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]. TLS-Sti A 'Service type... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.6.3 Outputs | Name Description QTSTo-Results An indication of the EU qualified status of the QTSP/QTS identified through the subject 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,... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.6.4 Processing | PRO-4.6.4-01: If Date-time is before "2016-06-30T22:00:00Z", then: a) the processing shall set QTSTo-Status to the value "PROCESS_PASSED"; b) the processing shall set QTSTo-Results to the set of values "Not_Qualified"; and c) the processing shall stop the process. PRO-4.6.4-02: The processing shall set CC to the countr... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.7 EU qualified time stamp determination | |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.7.1 Description | The procedure specified in clause 4.7 allows determining whether a time stamp token is confirmed by the applicable EUMS trusted list to have been an EU qualified time stamp at its generation time, provided that the timestamp is valid. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.7.2 Inputs | Name Description of inputs TST The time stamp token for which the information is to be obtained. Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1]. ETSI ETSI TS 119 615 V1.3.1 (2026-01) 40 |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.7.3 Outputs | Name Description QTST-Results An indication of the EU qualified status of TST through one of the following values: a) "Not_Qualified" to indicate that TST is not an EU qualified time stamp according to the EUMS trusted list from CC at Date-time; b) "Qualified" to indicate that TST is an EU qualified time stamp accordin... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.7.4 Processing | PRO-4.7.4-01: The processing shall set TLS-Sti to the value "http://uri.etsi.org/TrstSvc/Svctype/TSA/QTST" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.7.4-02: The processing shall run the process described in clause 4.6 of the present document, passing the following inputs to the process: a) CERT; b) T... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.8 EU qualified validation service determination | |
4028be74228292868d82461bedfe5a9b | 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 th... |
4028be74228292868d82461bedfe5a9b | 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]. ETSI ETSI TS 119 615 V1... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.8.3 Outputs | Name Description QVSO-Results A set of indications of the EU qualified status of the QTSP/QTS identified through the subject 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 l... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.8.4 Processing | PRO-4.8.4-01: 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.8.4-02: The processing shall run the process described in clause 4.6 of the present document, passing the following inputs to the process: a) CER... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.9 EU qualified preservation service determination | |
4028be74228292868d82461bedfe5a9b | 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 th... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.9.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]. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.9.3 Outputs | Name Description QPSO-Results A set of indications of the EU qualified status of the QTSP/QTS identified through the subject 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 l... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.9.4 Processing | PRO-4.9.4-01: 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.9.4-02: The processing shall run the process described in clause 4.6 of the present document, passing the following inputs to the process: a) CERT; b) TLS... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.10.1 Description | The procedure specified in clause 4.10 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 t... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.10.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]. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.10.3 Outputs | Name Description QERDSO-Results An indication of the EU qualified status of the QTSP/QTS identified through the subject 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... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.10.4 Processing | PRO-4.10.4-01: 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.10.4-02: 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 6... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.11 EU qualified archiving service determination | |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.11.1 Description | The procedure specified in clause 4.11 allows determining whether the signer identified in the certificate supporting the validation of the digital signature of a trust service output (e.g. the signature of the report of an electronic archiving service) is confirmed by the applicable EUMS trusted list to have been, at ... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.11.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]. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.11.3 Outputs | Name Description QARCH-Results An indication of the EU qualified status of the QTSP/QTS identified through the subject 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,... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.11.4 Processing | PRO-4.11.4-01: The processing shall set TLS-Sti to the value "http://uri.etsi.org/TrstSvc/Svctype/ElectronicArchiving/Q" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.11.4-02: The processing shall run the process described in clause 4.6 of the present document, passing the following inputs to the process... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.12.1 Description | The procedure specified in clause 4.12 allows determining whether an electronic attestation of attribute is confirmed by the applicable EUMS trusted list to have been an EU qualified electronic attestation of attribute at its generation time, provided that the electronic attestation of attribute is valid. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.12.2 Inputs | Name Description of inputs EAA The electronic attestation of attribute for which the information is to be obtained. Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1]. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.12.3 Outputs | Name Description QEAA-Results An indication of the EU qualified status of TST through one of the following values: a) "Not_Qualified" to indicate that EAA is not an EU qualified electronic attestation of attribute according to the EUMS trusted list from CC at Date-time; b) "Qualified" to indicate that EAA is an EU qual... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.12.4 Processing | PRO-4.12.4-01: The processing shall set TLS-Sti to the value "http://uri.etsi.org/TrstSvc/Svctype/EAA/Q" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.12.4-02: The processing shall set CERT to the X.509 certificate supporting the validation of the digital signature on EAA. PRO-4.12.4-03: The processing s... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.13 EU qualified ledger service determination | |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.13.1 Description | The procedure specified in clause 4.13 allows determining whether the signer identified in the certificate supporting the validation of the digital signature of a record on a ledger 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... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.13.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]. |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.13.3 Outputs | Name Description QLEDG-Results An indication of the EU qualified status of the QTSP/QTS identified through the subject 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,... |
4028be74228292868d82461bedfe5a9b | 119 615 | 4.13.4 Processing | PRO-4.13.4-01: The processing shall set TLS-Sti to the value "http://uri.etsi.org/TrstSvc/Svctype/Ledgers/Q" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.13.4-02: The processing shall run the process described in clause 4.6 of the present document, passing the following inputs to the process: a) CERT; b... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 1 Scope | The present document specifies protocols and interfaces applicable when the process of creating AdES digital signatures as defined by ETSI EN 319 102-1 [i.12] 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 sys... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 2 References | |
9bf343cc73a7e146e5fb853e898dc61a | 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 a... |
9bf343cc73a7e146e5fb853e898dc61a | 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 i... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 3 Definition of terms, symbols and abbreviations | |
9bf343cc73a7e146e5fb853e898dc61a | 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 that requests authorization from an Authorization Server on ... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 3.2 Symbols | Void. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Program Interface AS Authorization Server AS/SAM Authorization Server / Signature Activation Module CA Certification Authority CBOR Concise Binary Object Representation CEN European Committee for Standardization CMS Cryptograph... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 4 Signature creation process, service decomposition | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 4.1 Signature creation process steps and data elements | Figure 1 (derived from ETSI EN 319 102-1 [i.12], 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 av... |
9bf343cc73a7e146e5fb853e898dc61a | 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 request... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 4.3 Signature Creation Application | |
9bf343cc73a7e146e5fb853e898dc61a | 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, ... |
9bf343cc73a7e146e5fb853e898dc61a | 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 considered together, the SDR (hash of the document to be signed or hash of a formatted version of the document to be signed) and hashes of signed attributes/properties are assembled into the Data To Be Signed Forma... |
9bf343cc73a7e146e5fb853e898dc61a | 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. |
9bf343cc73a7e146e5fb853e898dc61a | 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). • ... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 4.4 Server Signing Application | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 4.4.1 Signature creation | |
9bf343cc73a7e146e5fb853e898dc61a | 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)... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 4.4.1.2 Signature activation | The SSASC uses a remote SCDev 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 possibly by means of the Signature Activation Module (SAM). The SAM is a software component using the Sig... |
9bf343cc73a7e146e5fb853e898dc61a | 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 va... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5 Authentication and authorization | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.1 Introduction | The present document recommends protecting remote signature creation services from unauthorized access. Any driving application shall be authenticated when invoking a signature creation service. In order to create signatures an authorization from the user who owns and controls the signing key is required. The user may ... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.2 Service authorization | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.2.1 Overview | Various types of authorization mechanisms may be supported, and the driving application shall adopt any of those available from the signature creation service. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.2.2 HTTP Basic Authentication and HTTP Digest Authentication | NOTE: HTTP Basic Authentication [i.10] is an unsafe mechanism, and therefore it should not be used, especially by driving application running as a service. It should only be used when there is a high degree of trust between the user and driving application and when other authorization types are not available. This mech... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.2.3 OAuth 2.0 | When the authentication is under the control of the signature creation service the signature creation service may adopt an indirect way of authorizing access to the API by using OAuth 2.0 [17] that is primarily an authorization framework, but that can also be leveraged for authentication when interacting with a signatu... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.2.4 Other authentication mechanisms | The underlying communication between the driving application and the signature creation service may ensure access control in some other different ways than OAuth 2.0 or HTTP Basic or Digest Authentication. The following alternatives can be considered for authenticating clients to a signature creation service: • Mutual ... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.3 Signatures creation authorization | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.3.1 Overview | Requesting signatures creation to a signature creation service requires an authorization from the user who owns and controls the signing key to be used for signatures creation. The user might authorize signatures creation with an already existing signing key or with a signing key to be created on-the-fly. Two different... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.3.3 Create a remote signature with a credential protected by OAuth2 | OAuth 2.0 authorization is a widely used framework that allows applications to obtain limited access to a user's resources on a service, without needing the user's authentication data (i.e. the user's password). OAuth 2.0 can provide client applications a secure delegated access to server resources on behalf of a resou... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.4 Credential creation authorization | Requesting credential creation to the signature creation service requires an authorization from the user to whom the credential to be created will be bound. CSC API [1] only supports OAuth 2.0 authorization to grant credential creation authorization. Figure 6: A general flow involving a driving application requesting s... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 5.5 Credential deletion authorization | A credential may be deleted for various reasons: • End of lifecycle: the credential is no longer needed or has expired. • Security reasons: the credential may be compromised or the user requests revocation. • Regulatory compliance: certain frameworks require deletion because of cryptographic algorithms obsolescence Req... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6 Architectures and use cases for server signing |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.