hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.1 Introduction | The following clauses describe a set of architectural models for the creation of remote electronic signatures, each distinguished by the mechanisms used to protect the signer's credential and to manage the authorization required for signature creation. The models differ in the interaction between components and in the ... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.1 Overview | In the European Union, Qualified Electronic Signatures (QES) are governed by the eIDAS Regulation [i.1]. This regulation defines the European Digital Identity Wallet (EUDIW) as an electronic identification means that enables users to securely store, manage, and validate personal identification data and electronic attes... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.3 EUDIW participating in the signature creation process | In the model outlined in Figure 20, the EUDIW coordinates AdES signature creation through a SCASC, that may be part of the EUDIW or of the EUDIW backend, interacting with the QTSP-operated SSASC. The Wallet Relying Party (WRP) can pass data to be signed by the EUDIW through a structured and regulated process that ensur... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4 EUDIW registration and authentication to authorization servers | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.1 Introduction | This clause defines the requirements for an EUDIW acting as an OAuth 2.0 client to register and authenticate to an authorization server using the OpenID Foundation FAPI 2.0 Security Profile [10], with explicit integration of Wallet Unit Attestation public key during dynamic client registration. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.2 EUDIW registration | • The authorization servers shall implement the FAPI 2.0 Security Profile and IETF RFC 7591 [11], OAuth 2.0 Dynamic Client Registration Protocol. • The authorization servers shall accept registration requests including client metadata values specified as claims in a software statement. • The EUDIW shall register dynami... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.3 EUDIW authentication | • The EUDIW shall implement OAuth 2.0 client capabilities. • The EUDIW shall use Authorization Code Flow with PKCE (IETF RFC 7636 [14]). • The EUDIW shall use PAR (IETF RFC 9126 [18]) with a signed JAR (IETF RFC 9101 [31]) for request integrity. • The EUDIW authentication at PAR and token endpoints shall be supported v... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.4 Security requirements | • The authorization server shall support issuance of sender-constrained access and refresh tokens by implementing the application-level mechanism Demonstrating Proof of Possession (DPoP), as specified in IETF RFC 9449 [25] as per FAPI. • The EUDIW shall sign the DPoP according to JWT syntax with the private key whose p... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.5 Examples | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.5.1 Dynamic Client Registration request payload (JSON) | POST /oauth/register HTTP/1.1 Host: as.example.eu Content-Type: application/json { "client_name": "European Digital Identity Wallet (MemberState-X)", "application_type": "native", "redirect_uris": [ "eudiwallet://cb", "https://wallet.example.ms/callback" ], "grant_types": ["authorization_code"], "response_types": ["cod... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.5.2 Authorization server response | HTTP/1.1 201 Created Content-Type: application/json Cache-Control: no-store { ETSI ETSI TS 119 432 V1.3.1 (2026-03) 47 "client_id": "client-9f7e2", "client_id_issued_at": 1736940201, "registration_access_token": "eyJraWQiOiJtZy0yMDI2LTAxIn0.eyJzY29wZSI6...", "registration_client_uri": "https://as.example.eu/oauth/regis... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.5.3 EUDIW authorization request payload (JSON) | FAPI 2.0 requires: • PAR (Pushed Authorization Request) for all authorization requests • JAR (JWT‑Secured Authorization Request) as the request object • response_type=code (only) • PKCE (S256) • sender‑constrained tokens (DPoP or mTLS) • Signed request object containing all parameters (AS ignores URL parameters except ... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.5.4 PAR Response (from AS to EUDIW) | HTTP/1.1 201 Created Content-Type: application/json Cache-Control: no-store { "request_uri": "urn:as:par:cx298dhasd98hasd9", "expires_in": 90 } request_uri can only be used once, an authorization server ignores all authorization request parameters except client_id and request_uri. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.5.5 Authorization Request (from EUDIW to authorization endpoint) | GET /authorize? client_id=client-12345& request_uri=urn:as:par:cx298dhasd98hasd9 HTTP/1.1 Host: as.example.eu This request contains almost nothing except client_id and request_uri. All security parameters are inside the signed JAR that was previously pushed via PAR. request URI points to the previously registered JAR a... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.4.5.6 Authorization server redirects back with authorization code | If the user authenticates successfully and consents, the authorization server redirects: HTTP/1.1 302 Found Location: eudiwallet://cb? code=SplxlOBeZQQYbYS6WxSbIA& state=af0ifjsldkj state is returned exactly as provided by the client, code is bound to the client through sender‑constrained token issuance with DPoP. Resp... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.5 DA / SCA registration and authentication to authorization servers | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.5.1 Introduction | This clause defines the requirements for a DA or a SCA acting as an OAuth 2.0 client to register and authenticate to an authorization server. In the following clauses the generic term "client" will be used to refer to DA or SCA. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 6.4.5.2 client registration | • The authorization server shall implement the FAPI 2.0 Security Profile and IETF RFC 7591 [11] OAuth 2.0 Dynamic Client Registration Protocol. • The authorization server shall accept registration requests including client metadata values specified as claims in a software statement. • The client may register dynamicall... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7 Remote signatures creation service API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.1 Introduction | In the present document the API represent the way by which any driving application can interact with any SCS conforming to the present document. The following clauses define the API that a driving application can invoke within an SCS. For any API the request and response messages pair is specified referring to CSC API ... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.2 Service information API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.2.1 Description | Returns information about the remote service and the list of the API methods it supports. The info API method referenced in CSC API [1], Clause 11.1 shall be applied and fully implemented to ensure compliance with the present document. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.2.2 Request message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.2.2.1 Component for requesting service information | The message for requesting the service information shall contain the components defined in CSC API [1], clause 11.1 section Input. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.2.3 Response message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.2.3.1 Component for responding to service information requests | The message for returning the service information shall contain the components defined in CSC API [1], clause 11.1 section Output with the addition of the components defined in Table 2. ETSI ETSI TS 119 432 V1.3.1 (2026-03) 51 Table 2 Parameter Presence Type Description oauth2FAPIsupport O boolean This parameter shall ... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.3 Credentials list API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.3.1 Description | Returns the list of credentials of a certain user. A user may have one or multiple credentials hosted by a single RSSP. If requested, it shall also return information about the signing certificate(s) and/or about the authorization mechanisms required to authorize the usage of the credentials for remote signing. The cre... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.3.2 Request message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.3.2.1 Component for requesting credentials list | The message for requesting the list of credentials shall contain the components defined in CSC API [1], clause 11.6 section Input. The parameter onlyValid needs not be supported. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.3.3 Response message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.3.3.1 Component for responding to credentials list requests | The message for returning the requested list of credentials information shall contain the components defined in CSC API [1], clause 11.6 section Output. The parameter onlyValid needs not be supported if the input parameter of the same name is not supported. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.4 Credentials info API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.4.1 Description | Retrieves a credential and returns information about signing certificate and authorization mechanisms required to authorize the usage of the credential for remote signing. The credentials/info API method referenced in CSC API [1], clause 11.7 shall be applied and may be implemented to ensure compliance with the present... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.4.2 Request message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.4.2.1 Component for requesting credential information | The message for requesting the information about a credential shall contain the components defined in CSC API [1], clause 11.7 section Input. ETSI ETSI TS 119 432 V1.3.1 (2026-03) 52 |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.4.3 Response message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.4.3.1 Component for responding to credential information requests | The message for returning the service information shall contain the components defined in CSC API [1], clause 11.7 section Output. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.5 Hash(es) signing API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.5.1 Description | Computes the digital signature of one or multiple hash values. The driving application shall pass the authorization data that allows the signing credential usage. The signatures/signHash API method referenced in CSC API [1], clause 11.13 shall be applied and fully implemented to ensure compliance with the present speci... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.5.2 Request message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.5.2.1 Component for requesting hash(es) signature creation | The message for requesting the hash(es) signature creation shall contain the components defined in CSC API [1], clause 11.13 section Input. The parameters operationMode, validity_period and response_uri need not be supported, so that only synchronous operation mode shall be supported by the SSASC. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.5.3 Response message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.5.3.1 Component for responding to hash(es) signature creation requests | The message for returning the signed hash(es) shall contain the components defined in CSC API [1], clause 11.13 section Output. The parameter responseID needs not be supported if the input parameter operationMode is not supported. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.6 Document(s) signing API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.6.1 Description | Creates one or more AdES signatures. The driving application shall pass the authorization data that allows the signing credential usage. The signatures/signDoc API method referenced in CSC API [1], clause 11.14 shall be applied and should be implemented to ensure compliance with the present specification. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.6.2 Request message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.6.2.1 Component for requesting documents signature creation | The message for requesting the hash(es) signature creation shall contain the components defined in CSC API [1], clause 11.14 section Input. The parameters operationMode, validity_period and response_uri need not be supported, so that only synchronous operation mode shall be supported by the SSASC. The values "C", "X" a... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.6.3 Response message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.6.3.1 Component for responding to documents signature creation requests | The message for returning the signed hash(es) shall contain the components defined in CSC API [1], clause 11.14 section Output. The parameter responseID needs not be supported if the input parameter operationMode is not supported. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.7 Signature(s) creation polling API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.7.1 Description | Returns the outcome corresponding to a previous signature(s) creation request when processed in asynchronous mode or the indication that the signing process has not yet been completed. The signatures/signPolling API method referenced in CSC API [1], clause 11.15 shall be applied. The signatures/signPolling API method n... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.7.2 Request message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.7.2.1 Component for polling previous signature creation requests | The message for requesting the responses corresponding to a previous signature(s) creation request shall contain the components defined in CSC API [1], clause 11.15 section Input. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.7.3 Response message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.7.3.1 Component for responding to polling previous signature creation requests | The message for returning the outcome of a previous signature creation request shall contain the components defined in CSC API [1], clause 11.15 section Output. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.8 Credentials creation API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.8.1 Description | The credentials/create API method identified in CSC API [1], clause 11.4 creates a new signing credential. If requested, it can also return the new signing certificate, the whole associated certificate chain, additional information about the signing certificate and/or information about the authorization mechanism requi... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.8.2 Request message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.8.2.1 Component for requesting credential creation | The message for requesting a credential creation shall contain the components defined in CSC API [1], clause 11.4 section Input. ETSI ETSI TS 119 432 V1.3.1 (2026-03) 54 |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.8.3 Response message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.8.3.1 Component for responding to credential creation requests | The message for returning the information of the newly created credential shall contain the components defined in CSC API [1], clause 11.4 section Output. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.8.4 Subject distinguished name of the new credential certificate | The remote signature creation service shall support the parameter subjectData given in the credentialCreationRequest input parameter in order to construct the subject distinguished name of the certificate for the new credential. When Rich Authorization Requests (RAR) are supported, the remote signature creation service... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.9 Credentials deletion API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.9.1 Description | The credentials/delete API identified in CSC API [1], clause 11.5 deletes a signing credential. This method requires credential deletion authorization. The credentials/delete API method referenced in CSC API [1], clause 11.5, shall be applied and may be implemented to ensure compliance with the present specification. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.9.2 Request message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.9.2.1 Component for requesting credential creation | The message for requesting a credential deletion shall contain the components defined in CSC API [1], clause 11.5 section Input. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.9.3 Response message | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 7.9.3.1 Component for responding to credential deletion requests | This API has no output values and the HTTP status code 204 "No Content", defined in clause 15.3.5 of IETF RFC 9110 [16], is provided in response as specified in CSC API [1], clause 11.5 section Output. ETSI ETSI TS 119 432 V1.3.1 (2026-03) 55 8 Remote signatures creation service API based on OASIS DSS-X |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.1 Introduction and General Provisions | In the present document, the API represent the way by which any client application can interact with any SCS conforming to the present document. The following clauses define the API that a client application can invoke within an SCS. For simplifying API mapping comparison, the subsequent sections presents DSS-X API ele... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.2 Service information API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.2.1 Description | Returns technical information about the service. OASIS DSS-X [4] provides various options for conveying service-specific information as detailed in clause 4 of [5] that represents a complementary standard document of DSS-X. The element name specification of clause 3.2 of [5] shall apply. ETSI ETSI TS 119 432 V1.3.1 (20... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.3 Credentials list API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.3.1 Description | Returns the list of credentials of a certain user. OASIS DSS-X [4] does not provide a specific API for requesting user credentials, which specifically protects privacy of the user by not exposing any credentials without explicit authentication or without user consent. By contrast, the metadata AuthInfo element (see cla... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.4 Credentials info API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.4.1 Description | Retrieves a credential and returns information about signing certificate and authorization mechanisms required to authorize the usage of the credential for remote signing. See clause 8.3 of the present document. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.5 Hash(es) signing API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.5.1 Description | Computes the digital signature of one or multiple hash values. For this purpose, the SignRequest with the DocumentHash variant of the InputDocuments component (see clause 4.5.5 of [4]) shall apply. The KeySelector component (see clause 4.4.12 of [4]) shall apply whenever the signing key cannot be determined implicitly. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.6 Document(s) signing API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.6.1 Description | Creates one or more AdES signatures. ETSI ETSI TS 119 432 V1.3.1 (2026-03) 57 For this purpose, the SignRequest with the Document variant of the InputDocuments component (see clause 4.5.3 of [4]) shall apply. For conveying more complex DTBS, particularly in the case of XAdES, the TransformedData variant (see clause 4.5... |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.7 Signature(s) creation polling API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.7.1 Description | Returns the outcome corresponding to a previous signature(s) creation request when processed in asynchronous mode or the indication that the signing process has not yet completed. For this purpose, the PendingRequest element (see clauses 4.3.5 and 7 of [4]) shall apply. |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.8 Credentials creation API | |
9bf343cc73a7e146e5fb853e898dc61a | 119 432 | 8.8.1 Description | The API credentials/create creates a new signing credential. OASIS DSS-X does not provide a specific API for signer certificate creation. This happens implicitly when the corresponding SignRequest implementation creates the signer certificate on the fly for single use, e.g. in the form of a validity-assured short-term ... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 1 Scope | The present document provides policy and security requirements for trust service providers (TSP) implementing a service component supporting AdES digital signature creation. This component contains a signature creation application and is thus called signature creation application service component (SCASC). However, it ... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 2 References | |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 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... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 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... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 3 Definition of terms, abbreviations and notations | |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.2] and the following apply: AdES (digital) signature: digital signature that is either a CAdES signature, or a PAdES signature or a XAdES signature digital signature: data appended to, or a cryptographic transformation of a data unit that a... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 119 001 [i.2] and the following apply: CA Certification Authority DTBS Data To Be Signed DTBSR Data To Be Signed Representation OID Object IDentifier ETSI ETSI TS 119 431-2 V1.1.1 (2018-12) 10 QES Qualified Electronic Signature or Qualified El... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 3.3 Notation | The requirements identified in the present document include: a) requirements applicable to any TSP conforming to the present document. Such requirements are indicated by clauses without any additional marking; b) requirements applicable under certain conditions. Such requirements are indicated by clauses marked by "[CO... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 4 General concepts | |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 4.1 General policy requirements concepts | The present document is structured in line with ETSI EN 319 401 [9]. It incorporates ETSI EN 319 401 [9] requirements by reference and adds requirements relevant for a SCASP. See ETSI EN 319 401 [9], clause 4 for guidance for guidance on general policy requirements. ETSI ETSI TS 119 431-2 V1.1.1 (2018-12) 11 4.2 Signat... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 4.2.1 Signature creation application service component practice statement | The signature creation application service provider (SCASP) develops, implements, enforces, and updates a SCASC practice statement which is a trust service practice statement such as defined in ETSI EN 319 401 [9], instantiated for a signature creation application service component. See clause 6.1. The SCASC practice s... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 4.2.2 Signature creation application service component policy | A SCASC policy describes what is offered and can contain diverse information beyond the scope of the present document to indicate the applicability of the service. A SCASC policy is defined independently of the specific details of the specific operating environment of a SSASP. The recipients of the service policy can b... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 4.2.3 Terms and conditions | In addition to the SCASC practice statement and, when issued by the SCASP, the SCASC policy, the SCASP also issues terms and conditions, see clause 6.2. Terms and conditions can cover a broad range of commercial terms or technical terms that are not necessarily communicated to the customer, etc. The terms and condition... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 4.2.4 Other documents associated with signature creation | Besides the description of the practices employed by the SCASP to offer the AdES digital signature creation service, it is important to document the criteria under which the signatures are created and, beyond this, can then be determined as fitting a certain business need. Two documents can be used for these purposes: ... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 4.3 Architecture | A TSP service component supporting AdES digital signature creation (SCASC) receives the document(s) and/or hash(es) of document(s) to be signed and optionally some signing parameters, collects all necessary information to create the signature, prepares the data-to-be-signed representation (DTBSR) and sends this to the ... |
18800a6bd4e1784f08d495a4a533ce1a | 119 431-2 | 5 Risk assessment | OVR-5-01: The requirements specified in ETSI EN 319 401 [9], clause 5 shall apply. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.