hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.14.4 Processing model
|
The client application can pass to the SCASC a particular value to be used for each attribute/property or leave the value up to the SCASC to be determined. If no value is passed and the SCASC cannot calculate it, the corresponding attribute/property shall not be included in the signature. The SCASC may include additional attributes/properties in the signature, even if these ones are not explicitly requested by the client application (i.e. because such attributes/properties are mandated by the signature profiles). ETSI ETSI TS 119 432 V1.2.1 (2020-10) 34
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.15 Component for protocol identifier
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.15.1 Component semantics
|
This component may be used by the client application to tell the server which protocol is being used to communicate to the server itself. The value of this component shall be an identifier notifying that the request has been built using the protocols defined by the present document. The identifier for the protocol defined by the present document shall be: • http://uri.etsi.org/19432/v1.1.1#/creationprofile# The request may contain additional components whose values are identifiers of other protocols that have also been used for building the request. This component shall be used to notify the server that the client expects processing of the request according to the protocols defined by the present document.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.15.2 JSON related component
|
The component to indicate the protocol used by the client application shall be represented by the following: • profile string type parameter. Specified according to table 15. Table 15 Parameter Type Description profile String String that identifies the protocol being used by the client application to communicate to SCS.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.15.3 XML related component
|
The element used to notify the server of the profile shall be the dsb:Profile element of the dss2:SignRequest, defined in OASIS DSS-v2.0 [2], clause 4.2.10.2.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.16 Component for requesting specific signature formats
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.16.1 Component semantics
|
This component is used to request a specific signature format. The signature format and conformance level shall be the same for each document that will be signed within the identified signature request. The conformance levels of the "baseline profiles" standards, defined in ETSI EN 319 122-1 [11], ETSI EN 319 132-1 [12], ETSI EN 319 142-1 [13], should be used. The conformance levels of the "baseline profiles" standards, defined in ETSI TS 103 171 [i.10], ETSI TS 103 172 [i.11], and ETSI TS 103 173 [i.9], may be used. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 35 Table 16 Signature format Conformance level URI CAdES/PAdES/XAdES AdES-B-B http://uri.etsi.org/ades/191x2/level/baseline/B-B# CAdES/PAdES/XAdES AdES-B-T http://uri.etsi.org/ades/191x2/level/baseline/B-T# CAdES/PAdES/XAdES AdES-B-LT http://uri.etsi.org/ades/191x2/level/baseline/B-LT# CAdES/PAdES/XAdES AdES-B-LTA http://uri.etsi.org/ades/191x2/level/baseline/B-LTA# CAdES/PAdES/XAdES AdES-B http://uri.etsi.org/ades/etsits/level/baseline/B-B# CAdES/PAdES/XAdES AdES-T http://uri.etsi.org/ades/etsits/level/baseline/B-T# CAdES/PAdES/XAdES AdES-LT http://uri.etsi.org/ades/etsits/level/baseline/B-LT# CAdES/PAdES/XAdES AdES-LTA http://uri.etsi.org/ades/etsits/level/baseline/B-LTA# According to the type of signature selected a client may also specify the following signature properties. Table 17 Signature format Signed envelope property URI CAdES Detached Attached Parallel http://uri.etsi.org/cades/detached# http://uri.etsi.org/cades/attached# http://uri.etsi.org/cades/parallel# PAdES Certification Revision http://uri.etsi.org/pades/certification# http://uri.etsi.org/pades/revision# XAdES Enveloped Enveloping Detached http://uri.etsi.org/xades/enveloped# http://uri.etsi.org/xades/enveloping# http://uri.etsi.org/xades/detached#
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.16.2 JSON related component
|
The component for requesting a specific signature format shall be represented by the following parameters: • signatureFormat string type parameter; • conformanceLevel string type parameter; • signedEnvelopeProperty string type parameter. Specified according to table 18. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 36 Table 18 Parameter Presence Type Description signatureFormat Required String The required signature format: • "C" shall be used to request the creation of a CAdES signature; • "X" shall be used to request the creation of a XAdES signature; • "P" shall be used to request the creation of a PAdES signature. conformanceLevel Optional String • "AdES-B-B" shall be used to request the creation of a baseline 191x2 level B signature. • "AdES-B-T" shall be used to request the creation of a baseline 191x2 level T signature. • "AdES-B-LT" shall be used to request the creation of a baseline 191x2 level LT signature. • "AdES-B-LTA" shall be used to request the creation of a baseline 191x2 level LTA signature. • "AdES-B" shall be used to request the creation of a baseline etsits level B signature. • "AdES-T" shall be used to request the creation of a baseline etsits level T signature. • "AdES-LT" shall be used to request the creation of a baseline etsits level LT signature. • "AdES-LTA" shall be used to request the creation of a baseline etsits level LTA signature. The parameter is optional. The default baseline level is AdES-B-B in case it is omitted. If a timestamp is needed its request and inclusion is managed by the SCS according to SCS configuration and policies. signedEnvelopeProperty Optional Conditional String The required property concerning the signed envelope whose possible values depend on the value of the signatureFormat parameter.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.16.3 XML related component
|
The element for requesting a specific signature format shall be the etsisig:SignatureType, child element of the dss2:OptionalInputs element. It shall contain a URI reference to the predefined signature type the server shall produce, with values as specified in clause 7.16.1. The element for requesting a specific signature conformance level shall be etsisig:ConformanceLevel, child element of the dss2:OptionalInputs element. It shall contain a URI reference to the predefined conformance level at which the server shall produce the signature. The element for specifying the envelope property shall be etsisig:SignedEnvelopeProperty. Its possible values depend on the specified envelope type and are defined in clause 7.16.1. <xs:element name="ConformanceLevel" type="xs:anyURI"/> <xs:element name="SignatureType" type="xs:anyURI"/> <xs:element name="SignedEnvelopeProperty" type="xs:anyURI"/> The table defined in clause 7.16.1 lists URIs for the levels specified for AdES signatures in ETSI EN 319 122-1 [11], ETSI EN 319 132-1 [12], ETSI EN 319 142-1 [13], ETSI TS 103 171 [i.10], ETSI TS 103 172 [i.11], and ETSI TS 103 173 [i.9]. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 37
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.17 Component for signer identification
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.17.1 Component semantics
|
This component is used to uniquely identify the signer. This component represents the signer identifier associated to the signer identity within the SCS. A request shall contain a component for signer identification. NOTE: This component can be accepted or rejected by the server based on the current service authentication (i.e. in order to avoid to obtain the list of credentials associated to a signer not bound to the current service authentication).
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.17.2 JSON related component
|
The component for specifying the signer identification shall be represented by the following: • SignerIdentity string type parameter. Specified according to table 19. Table 19 Parameter Type Description SignerIdentity String The identifier associated to the signer identity.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.17.3 XML related component
|
The element for signer identification shall be the etsisig:SignerIdentity element, child element of etsisig:OptionalInputs. The etsisig:SignerIdentity 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="SignerIdentity" type="dss2:ClaimedIdentityType"/> The type dss2:ClaimedIdentityType is defined in OASIS DSS-v2.0 [2], clause 4.4.9.2.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.18 Component for specifying response URL
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.18.1 Component semantics
|
With this component a client application can communicate to the SCS a response URL where the client expects to receive a notification when the SCS has completed the requested operation. This component shall contain an absolute URL.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.18.2 JSON related component
|
The component for specifying the response URL where the client application requests to receive the notification of the completed operation shall be represented by the following: • responseUri string type parameter. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 38 Specified according to table 20. Table 20 Parameter Type Description responseUri String The element shall have the value of one location where the SCS will notify the signature creation operation completion, as an URI value.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.18.3 XML related component
|
The element for specifying the response URL shall be etsisig:ResponseURL, child element of the dss2:OptionalInputs element. The etsisig:ResponseURL element shall be defined as in XML schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2 and is copied below for information: <xs:element name="ResponseURL" type="xs:anyURI"/>
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.18.4 Processing model
|
If this component is present and the SCS performs the requested operation in asynchronous operation mode, the SCS shall invoke the location specified by this component after the completion of the requested operation. The SCS shall provide as input parameter the component specified in clause 7.26 that the client application can include in the subsequent request, polling the pending signature results. 7.19 Component for submitting document(s) or hash(es) to be signed
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.19.1 Component semantics
|
This component shall be used to pass to the SCS the list of document(s) or the list of hash(es) for which the signature(s) generation is requested. Document(s) and hash(es) shall be provided either in: • a container containing the base-64 encoded content(s) of the document(s) to be signed; or in • a container containing the base-64 encoded hash(es) of the document(s) to be signed and the digest algorithm used to calculate such hash(es). Therefore an instance of this component shall not contain both a list of documents and a list of hashes. Table 20 contains a list of hashing algorithms recommended in ETSI TS 119 312 [i.4]. Table 21 Hash algorithm OID Hash algorithm name Hash algorithm URI 2.16.840.1.101.3.4.2.1 SHA-256 http://www.w3.org/2001/04/xmlenc#sha256 2.16.840.1.101.3.4.2.2 SHA-384 http://www.w3.org/2001/04/xmldsig-more#sha384 2.16.840.1.101.3.4.2.3 SHA-512 http://www.w3.org/2001/04/xmlenc#sha512 2.16.840.1.101.3.4.2.8 SHA3-256 http://www.w3.org/2007/05/xmldsig-more#sha3- 256 2.16.840.1.101.3.4.2.9 SHA3-384 http://www.w3.org/2007/05/xmldsig-more#sha3- 384 2.16.840.1.101.3.4.2.10 SHA3-512 http://www.w3.org/2007/05/xmldsig-more#sha3- 512 ETSI ETSI TS 119 432 V1.2.1 (2020-10) 39
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.19.2 JSON related component
|
The component for submitting document(s) or hash(es) to be signed shall be represented by the following (mutually exclusive) parameters: • documents: array of string type parameter. • documentDigests: JSON objects containing hash(es) to be signed and the digest algorithm OID used to calculate the hash(es) specified according to table 22. Table 22 Parameter Presence Type Description documents Required Conditional Array of String Base64-encoded document(s) content(s), to be signed. This parameter shall not be used if the parameter documentDigests is passed. documentDigests Required Conditional JSONObject JSON Object containing hash(es) to be signed and digest algorithm OID used to calculate di hash(es). This parameter shall not be used if the parameter documents is passed. The documentDigests element shall be a JSONObject containing the following parameters: • hashes array of string type parameter. • hashAlgorithmOID string type parameter. Specified according to table 23. Table 23 Parameter Presence Type Description hashes Required Array of String Base64-encoded document(s) hash(es), to be signed. hashAlgorithmOID Required String Hashing algorithm OID used to calculate document hash(es).
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.19.3 XML related component
|
The element for submitting documents and hashes shall be dss2:InputDocuments, with values as specified in OASIS DSS-v2.0 [2], clause 4.5.1.2.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.20 Component for returning service information
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.20.1 Component semantic
|
This element shall contain: 1) a general description of the service; 2) a general name identifying the service; 3) a pointer to the logo of the service; 4) the country where the service is operating; 5) information concerning the protocol supported, i.e. the URI http://uri.etsi.org/19432/v1.1.1/creationprofile# specifies the support of the profile specified in the present document; 6) a list of the versions of the protocol supported; 7) a list of supported languages, the first language in the list being the SCS default language; ETSI ETSI TS 119 432 V1.2.1 (2020-10) 40 8) a list of signature policies implemented by the SCS; 9) a list of service policies implemented by the SCS; 10) a list of accepted operation modes; 11) a list of supported authentication modes; 12) a list of signature formats, conformance levels and signed envelope properties; 13) a list of names of all the API methods implemented and supported by the SCS. Some of the above items may be empty or absent indicating a feature not being supported by the SCS.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.20.2 JSON related component
|
The component for returning service information shall be represented by the following 1) description string type result; 2) name string type result; 3) logo string type result; 4) region string type result; 5) protocol string type result; 6) versions array of string type result; 7) lang array of string type result; 8) signaturePolicies an array of strings result; 9) servicePolicies an array of strings result; 10) operationModes an array of strings result; 11) authType an array of strings result; 12) signatureFormats an array of signature format, conformance level and signed envelope property values defining which values may be passed in the component defined in clause 7.16; 13) methods an array of strings result. Specified according to table 24. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 41 Table 24 Parameter Presence Value Description description Required String A short description of the service. name Required String The name of the service. logo Required String The URI of the image file containing the logo of the Service. The image shall be in either JPEG or PNG format and not larger than 256x256 pixels. region Required String The ISO 3166-1 [14] alpha-2 country code where the service is operating. protocol Required String The URI identifying the protocol supported by the SCS. versions Required Array of String The versions of the protocol specifications supported by the SCS. The format of the strings is Major.Minor.x. lang Required Array of String List of the supported languages in the service responses, specified according to IETF RFC 5646 [7]. signaturePolicies Required Array of String List of the supported signature policies. servicePolicies Required Array of String List of the supported service policies. operationModes Required Array of String List of the supported operation modes. authType Required Array of String List of the authentication mechanisms supported by the service for API methods access. signatureFormats Required Array of JSONObject List of JSONObject specifying the signature formats supported by the SCS and containing the following parameters: • signatureFormat string type parameter; • conformanceLevel string type parameter; • signedEnvelopeProperty string type parameter. as specified in clause 7.16.2. methods Required Array of String List of the supported API methods names. The "signatureFormats", "signaturePolicies", "servicePolicies" and "operationModes" elements are not defined in CSC standard [1]. The other elements are defined in clause 11.1 of the CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.20.3 XML related component
|
The element for returning service information shall be etsisig:ServiceInformation child element of the etsisig:OptionalOutputs. The ServiceInformation 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="ServiceInformation" type="etsisig:ServiceInformationType"/> <xs:complexType name="ServiceInformationType"> <xs:sequence> <xs:element name="Description" type="xs:string"/> <xs:element name="Version" type="xs:string"/> <xs:element name="Logo" type="xs:anyURI"/> <xs:element name="Region" type="xs:string"/> <xs:element name="SupportedProtocol" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SupportedLanguage" type="xs:language" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SupportedSignaturePolicy" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SupportedServicePolicy" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SupportedOperationMode" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SupportedSignatureFormat" type="etsisig:SupportedSignatureFormatType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SupportedAuthMode" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SupportedMethod" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="SupportedSignatureFormatType"> <xs:sequence> <xs:element name="SupportedSignatureType" type="xs:anyURI" minOccurs="0"/> <xs:element name="SupportedConformanceLevel" type="xs:anyURI" minOccurs="0"/> <xs:element name="SupportedEnvelope" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:complexType> ETSI ETSI TS 119 432 V1.2.1 (2020-10) 42
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.21 Component for returning signed documents or signatures
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.21.1 Component semantics
|
This component shall be used to return the requested signatures. The protocol shall allow returning the signatures in two different containers according to the following rules: 1) If the signature is enveloped within the signed document, it shall be included in a specific container identified as the container for the signed document. 2) If the signature is not enveloped then it shall be included in a specific container identified as the container that encloses the signature. The protocol supports either a 1-to-1 relation between input documents and signatures or a many-to-1 relation where all input documents are covered by one signature.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.21.2 JSON related component
|
The component for returning the requested signed documents or signatures shall be represented by the following: • DocumentWithSignature: JSON array of string type result; • SignatureObject: JSON array of string type result; Specified according to table 25. Table 25 Parameter Presence Type Description DocumentWithSignature Required Conditional Array of String Base64-encoded signatures enveloped within the documents. This element shall carry a value only if the client application requested the creation of signature(s) enveloped within the signed document(s). SignatureObject Required Conditional Array of String Base64-encoded signatures detached from the documents. This element shall carry a value only if the client application requested the creation of not enveloped signature(s).
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.21.3 XML related component
|
The element for returning signatures shall be dss2:SignatureObject, with values as specified in OASIS DSS-v2.0 [2], clause 4.5.6.2. In the case of signatures enveloped in documents, the dss2:DocumentWithSignature element, defined in OASIS DSS-v2.0 [2] clause 4.4.19.2, shall be used.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.22 Component for returning signing credential information
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.22.1 Component semantics
|
This component is used for returning signing certificate chain/signing certificate credential information. This component shall contain information about the signing certificate credential and the signing certificate chain used or to be used in the operation of DSV(s) or signatures creation. This component shall contain the following data: 1) the signing X.509 certificate/chain; 2) information about the signing key: - status of the key; ETSI ETSI TS 119 432 V1.2.1 (2020-10) 43 - algorithms supported; - length of the key; - curve; 3) the signer certificate attribute details: - status; - validFrom; - validTo; - issuerDN; - serialNumber; - subjectDN; 4) the support of multiple signatures creation with a single authorization request specification by the credential. The inclusion of this component in the response may be requested by the client application using the "Component for defining optional data to be returned" defined in clause 7.5. The information about signing X.509 certificate/chain and/or signing key to be included in this component may be specified by the client application using the "Component for specifying the contents from certificate info to be returned" defined in clause 7.10.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.22.2 JSON related component
|
The component for returning signing certificate/credential information shall be represented by the following: • cert/certificates: array of string type result; • key/status: string type result; • key/algo: array of string type result; • key/len: integer type result; • key/curve: string type result; • cert/status: string type result; • cert/validFrom: string type result; • cert/validTo: string type result; • cert/IssuerDN: string type result; • cert/serialNumber: string type result; • cert/subjectDN: string type result; • multisign: Boolean type result. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 44 Specified according to table 26. Table 26 Parameter Presence Type Description cert/certificates Required Conditional Array of String Contains one or more Base64-encoded X.509v3 certificates from the certificate chain. If the certificates parameter defined in clause 7.10.1.2 is "chain", the entire certificate chain shall be returned with the end entity certificate at the beginning of the array. If the certificates parameter is "single", only the end entity certificate shall be returned. If the certificates parameter is "none", this parameter shall not be returned. key/status Required String Enabled | Disabled: • The status of enablement of the signing key of the credential: • "enabled": the signing key is enabled and can be used for signing. • "disabled": the signing key is disabled and cannot be used for signing. This may occur when the owner has disabled it or when the SCS has detected that the associated certificate is expired or revoked. key/algo Required String The list of OIDs of the supported key algorithms. For example: 1.2.840.113549.1.1.1 = RSA encryption, 1.2.840.10045.4.3.2 = ECDSA with SHA256, 1.2.840.113549.1.1.10 = RSASSA-PSS, 1.2.840.10045.4.3.4 = ECDSA with SHA512. key/len Required Number The length of the cryptographic key in bits. key/curve Required Conditional String The OID of the ECDSA curve. The value shall only be returned if keyAlgo is based on ECDSA. cert/status Optional String valid | expired | revoked | suspended: The status of validity of the end entity certificate. The value is optional. The SCS shall only return a value that is accurate and consistent with the actual validity status of the certificate at the time the response is generated otherwise this parameter shall not be included in the response. The "valid" status shall be returned when the certificate is in the validity period, is generated by a CA trusted by the SCS and is not revoked or suspended. Therefore the SCS shall not include this parameter in the response if it cannot check if the signing certificate is revoked, suspended or not. cert/validFrom Required String The validity start date from the X.509v3 signing certificate in printable string format, encoded as GeneralizedTime format (IETF RFC 5280 [4]) (e.g. "YYYYMMDDHHMMSSZ"). This parameter shall be returned when certInfo defined in clause 7.10 is "true". cert/validTo Required String The validity end date from the X.509v3 signing certificate in printable string format, encoded as GeneralizedTime format (IETF RFC 5280 [4]) (e.g. "YYYYMMDDHHMMSSZ"). This parameter shall be returned when certInfo defined in clause 7.10 is "true". cert/IssuerDN Required Conditional String The Issuer Distinguished Name from the X.509v3 end entity certificate in printable string format, UTF-8-encoded according to IETF RFC 4514 [8]. This parameter shall be returned when certInfo defined in clause 7.10 is "true". cert/serialNumber Required Conditional String The Serial Number from the X.509v3 certificate in hex encoded format. This parameter shall be returned when certInfo defined in clause 7.10 is "true". cert/subjectDN Required Conditional String The Subject Distinguished Name from the X.509v3 certificate in printable string format, UTF-8-encoded according to IETF RFC 4514 [8]. This parameter shall be returned when certInfo defined in clause 7.10 is "true". multisign Required Conditional Boolean Specifies if the credential supports multiple signatures to be created with a single authorization request. The above elements are defined in clause 11.5 of the CSC standard [1]. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 45
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.22.3 XML related component
|
The element for returning signing certificate/credential/chain shall be ds:KeyInfo, child element of the dss2:OptionalOutputs root element. The element for returning signing certificate/credential/chain information shall be ds:X509Data, child element of the ds:KeyInfo element. To include additional attributes as listed in point 3 in the semantics clause above, the etsisig:X509Details element shall be used in the corresponding element of ds:KeyInfo. The X509Details 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="X509Details" type="etsisig:X509DetailsType"/> <xs:complexType name="X509DetailsType"> <xs:sequence> <xs:element ref="etsisig:Status"/> <xs:element ref="etsisig:NotBefore"/> <xs:element ref="etsisig:NotAfter"/> </xs:sequence> </xs:complexType> <xs:element name="NotBefore" type="xs:dateTime"/> <xs:element name="NotAfter" type="xs:dateTime"/> <xs:element name="Status" type="etsisig:CertificateStatusType"/> <xs:simpleType name="CertificateStatusType"> <xs:restriction base="xs:string"> <xs:enumeration value="Valid"/> <xs:enumeration value="Expired"/> <xs:enumeration value="Revoked"/> <xs:enumeration value="Suspended"/> </xs:restriction> </xs:simpleType> <xs:element name="Enabled" type="xs:Boolean"/> <xs:element name="Algorithm" type="xs:anyURI"/> <xs:element name="Length" type="xs:int"/> <xs:element name="Curve" type="xs:anyURI"/> <xs:element name="KeyDetails" type="etsisig:KeyDetailsType"/> <xs:complexType name="KeyDetailsType"> <xs:sequence> <xs:element ref="etsisig:Enabled"/> <xs:element ref="etsisig:Algorithm"/> <xs:element ref="etsisig:Length"/> <xs:element ref="etsisig:Curve"/> </xs:sequence> </xs:complexType> <xs:element name="MultipleSignaturesEnabled" type="xs:Boolean"/> EXAMPLE: <ds:KeyInfo> <ds:X509Data> <etsisig:X509Details> <etsisig:Status>Valid</etsisig:Status> <etsisig:NotBefore>2002-05-30T09:00:00</etsisig:NotBefore> <etsisig:NotAfter>2022-05-30T09:00:00</etsisig:NotAfter> </etsisig:X509Details> <etsisig:KeyDetails> <etsisig:Enabled>true</etsisig:Enabled> <etsisig:Algorithm>1.2.840.10045.4.3.2</etsisig:Algorithm> <etsisig:Length>4096</etsisig:Length> <etsisig:Curve>1.2.840.10045.3.1.1.7</etsisig:Curve> </etsisig:KeyDetails> <etsisig:MultipleSignaturesEnabled>false</etsisig:MultipleSignaturesEnabled> </ds:X509Data> </ds:KeyInfo> ETSI ETSI TS 119 432 V1.2.1 (2020-10) 46
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.23 Component for returning the list of the signing certificate(s)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.23.1 Component semantics
|
This component shall be used for returning available signing certificate(s) of the signer. Each signing certificate may also include its chain.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.23.2 JSON related component
|
The component for returning available signing certificate(s) of the signer shall be represented by the following: • credentialIDs array of string type parameters; • certificates array of string type parameters. Specified according to table 27. Table 27 Parameter Presence Type Description credentialIDs Required Array of String One or more credentialIDs associated with the provided or implicit signer identification. certificates Conditional Array of String Each String shall contains one or more certificates from the signing certificate chain, each certificate textually encoded as specified in clause 5 of IETF RFC 7468 [10]. If the certificates parameter defined in clause 7.10.1.2 is "chain", each string shall contain the entire certificate chain with the end entity certificate at the beginning of the string and more additional CAs certificates following. If the certificates parameter is "single", each string shall contain only the end entity certificate. If the certificates parameter is "none", this parameter shall not be returned.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.23.3 XML related component
|
The element for returning the list of the signing certificate(s) shall be ds:KeyInfo, child element of the etsisig:OptionalOutputs root element. If the ReturnCertificates parameter defined in clause 7.10.3 clause is "Chain", the entire certificate chain shall be returned with the end entity certificate as the first ds:Keyinfo element. If the ReturnCertificates parameter is "Single", only the end entity certificate shall be returned. If the ReturnCertificates parameter is "None", no ds:Keyinfo element shall be returned.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.24 Component for notifying operation result(s)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.24.1 Component semantics
|
This component shall contain information representing the outcome(s) of the request. NOTE: When the requesting mode is synchronous this component will return the outcome(s) of the processing. When the requesting mode is asynchronous this component will return the confirmation or not of the acceptance of the request.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.24.2 JSON related component
|
When the HTTP status of the request is different from 200 OK, the outcome(s) of the requested operation shall be returned in the body of the HTTP response using the "application/json" media type. The JSON structure includes the following: • error string type value; ETSI ETSI TS 119 432 V1.2.1 (2020-10) 47 • error_description string type value. Specified according to table 28. Table 28 Parameter Presence Type Description error Required String An error code string. error_description Optional String A human readable description, written in a language that considers the lang parameter specification, providing additional error information to assist the client application in understanding the error that occurred. The status codes and error messages defined in clause 10.1 of CSC standard [1] shall be used if applicable.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.24.3 XML related component
|
The element for notifying the result shall be the dsb:Result with values of child elements dss2:ResultMajor and dss2:ResultMinor as specified in OASIS DSS-v2.0 [2], clause 4.2.7.2.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.25 Component for service policy identification
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.25.1 Component semantics
|
This component shall be used to return the name of the service policy used by the server to perform the requested operation. The inclusion of this component in the response may be requested by the client using the "Component for defining optional data to be returned" defined in clause 7.5.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.25.2 JSON related component
|
The component for returning the service policy identification shall be represented by the following: • policy string type result. Specified according to table 29. Table 29 Parameter Type Description policy String The element that identifies a particular service policy associated with the SCS.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.25.3 XML related component
|
The element for service policy identification shall be dsb:AppliedPolicy, child element of the dss2:OptionalOutputs element, defined in OASIS DSS-v2.0 [2], clause 4.2.9.2.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.26 Component for identification of the response
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.26.1 Component semantics
|
This component contains a string value generated by the SCS uniquely identifying the response originated from the SCS itself. This component is mainly used in asynchronous operation mode where the client application shall provide the responseID value received with the initial response included in the requestID component of any subsequent request polling the pending signature results. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 48
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.26.2 JSON related component
|
The component for identifying the signature request whose results are requested shall be represented by the following: • responseID string type parameter. Specified according to table 30. Table 30 Parameter Type Description responseID String Arbitrary string value generated by the SCS uniquely identifying the response originated from the SCS itself.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.26.3 XML related component
|
The element for identifying the signature request whose results are requested shall be the responseID attribute of the element dss2:SignResponse root element, defined in OASIS DSS-v2.0 [2], clause 4.3.2.2.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.27 Component for signature creation policy identification
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.27.1 Component semantics
|
This component shall contain information used to generate signature(s) and/or DSV(s). The information shall contain: a) The identification of the signature creation policy used while creating the DSV(s). b) Other optional parameters containing the locations of the signature creation policy document. The inclusion of this component in the response may be requested by the client using the "Component for defining optional data to be returned" defined in clause 7.5. NOTE: The signature creation policy may be a part of the service policy. The signature creation policy may therefore be implicitly identified by the applied service policy.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.27.2 JSON related component
|
The component for returning the signature creation policy identification shall be represented by the following: • signaturePolicyID string type parameter; • signaturePolicyLocations array of string type parameter. Specified according to table 31. Table 31 Parameter Presence Type Description signaturePolicyID Required String The element that identifies a particular policy associated with the SCS. It 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]. signaturePolicyLocations Optional Array of String Every string element shall have as an URI value the value of one location where the signature creation policy document can be accessed. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 49
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.27.3 XML related component
|
The element for the signature creation policy identification shall be dsb:AppliedPolicy, child element of the dss2:OptionalOutputs element, defined in OASIS DSS-v2.0 [2], clause 4.2.9.2.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.28 Component for returning credential authorization mode
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.28.1 Component semantics
|
This component specifies the authorization mode required by the identified signature credential. EXAMPLE: The SCSP can specify the supported authorization modes in the service policy or in the terms and conditions of the service. Returned values may be: 1) "implicit": the authorization process is managed by the SCS autonomously. In such mode the SCS will deal directly with the user in order to perform the authorization process without any involvement of the client application; 2) "explicit": the client application provides the needed factors of security elements to the SCS for the SCS to perform the authorization process; 3) "authorizationCode": the authorization process is managed by the SCS using a mechanism based on authorization code, for example an OAuth 2.0 mechanism based on authorization code as described in IETF RFC 6749 [i.5]; 4) "identificationToken": the authorization process is managed by the SCS using a mechanism based on security tokens containing user profile information (like the user's name, email, and so forth), represented in the form of claims (for example a JWT as described in IETF RFC 7519 [i.6] or a SAML assertion); or 5) other different values according to the authorization modes supported and specified by the SCSP.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.28.2 JSON related component
|
The component for returning the authorization mode of the identified signature credential shall be represented by the following: • authMode string type result. Specified according to table 32. Table 32 Parameter Type Description authMode String Specifies the authorization mode of the signature credential. The "authMode" element is defined in clause 11.5 of the CSC standard [1]. The value "identificationToken", mentioned in clause 7.28.1, is not defined in CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.28.3 XML related component
|
The element for returning credential authorization mode shall be etsisig:AuthorizationMode, child element of the etsisig:OptionalOutputs element. The etsisig:AuthorizationMode 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="AuthorizationMode" type="AuthorizationModeType"/> <xs:simpleType name="AuthorizationModeType"> <xs:restriction base="xs:string"> ETSI ETSI TS 119 432 V1.2.1 (2020-10) 50 <xs:enumeration value="Implicit"/> <xs:enumeration value="Explicit"/> <xs:enumeration value="AuthorizationCode"/> <xs:enumeration value="IdentificationToken"/> </xs:restriction> </xs:simpleType>
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.29 Component for returning digital signature value(s)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.29.1 Component semantics
|
This component shall contain a list of base64 encoded signature values corresponding to the DTBSR(s) passed in the documentDigests parameter specified in clause 7.19. The digital signature value(s) position in the list shall be the same as the ones of the hashes included in the DTBSR(s) component. The values returned in this component may be specified according to possible alternative behaviours of the SCS: 1) When one or more of the requested signatures fail, this component is not returned and an error code is returned as signature creation result outcome(s). 2) When one or more of the requested signatures fail, the corresponding DSV(s) are returned as empty values.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.29.2 JSON related component
|
The component for returning the DSV(s) shall be represented by the following: • signatures array of string type result. Specified according to table 33. Table 33 Parameter Type Description signatures Array of String One or more base64-encoded signature value(s). In case of multiple signatures, the signatures values shall be returned in the same order as the corresponding hashes provided as an input parameter.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.29.3 XML related component
|
The element for returning digital signature value(s) shall be dss2:SignatureObject, child element of the dss2:SignResponse root element, defined in OASIS DSS-v2.0 [2], clause 4.5.6.2. There shall be one dss2:SignatureObject for each DSV. The optional attribute WhichDoc shall contain the identifier of the related document from the signature creation request. 7.30 Component for returning sole control assurance level required
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.30.1 Component semantics
|
This component specifies the sole control assurance level required by the identified signature credential, as defined in CEN EN 419 241-1 [6]. Only two values of sole control assurance level shall be supported: "SCAL1" and "SCAL2". Such values identify two different levels of confidence of the control of the signing key, as specified in clause 4.4.1.1. NOTE: With regards to the present document, the "SCAL2" value indicates that the signature activation data, used in order to ensure the authorized signer's use of its signing key, is linked to the document or the documents to be signed and that a two-factor authorization is needed to authorize a signature. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 51
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.30.2 JSON related component
|
The component for returning the sole control assurance level required by the identified signature credential shall be represented by the following: • SCAL string type result. Specified according to table 34. Table 34 Parameter Type Description SCAL String Specifies the Sole Control Assurance Level required by the credential: • "1": the sole control assurance level 1 is required by the identified signature credential. • "2": the sole control assurance level 2 is required by the identified signature credential. The "SCAL" element is defined in clause 11.5 of the CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
7.30.3 XML related component
|
The element for returning SCAL level required shall be etsisig:SoleControlAssuranceLevel, child element of the etsisig:OptionalOutputs element. The SoleControlAssuranceLevel 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="SoleControlAssuranceLevel" type="SoleControlAssuranceLevelType"/> <xs:simpleType name="SoleControlAssuranceLevelType"> <xs:restriction base="xs:string"> <xs:enumeration value="SCAL1"/> <xs:enumeration value="SCAL2"/> </xs:restriction> </xs:simpleType>
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8 Remote signature creation messages
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.1 Introduction
|
In the present document the messages represent the way in which any client application can interact with any SCS conforming to this specification. The following clauses define the messages that a client application and an SCS can exchange. For any request and response pair it is specified which of the components defined in the previous clause can be used, by means of a table where the following information are provided: • the reference to the clause where the component is specified; • a brief description of the component; • the presence of the component. The value included in the column "Presence" of the tables 36 to 47 has the meaning defined in table 35. Table 35 Value Description M The component shall be included in the request to or response from the SCS. O The component may be included in the request to or response from the SCS. C The component shall be included in the request or response based on the occurrence of certain conditions. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 52
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.2 AdES signatures creation messages
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.2.1 Request message (A)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.2.1.1 Component for requesting AdES signatures creation
|
The message for requesting the creation of AdES signatures to an SCASC shall contain components for: 1) Submitting either the documents to be signed or the SDR (signer's document representation, for example the hash value of the document). NOTE 1: The message may contain one or more documents and/or one or more document representations for signature creation. An AdES signature will be created for each of these input components. Other components are used to select the type of signature that will be created for each document or document hash. 2) Providing credential authorization in the form of signature activation data. 3) Identifying one or more protocols and/or profiles with which the request message is compliant. The first one of such components shall have the following URI as value, identifying the request message as one that has been built using the "AdES signature creation" protocol specified in the present document: - http://uri.etsi.org/19432/v1.1.1/signaturecreationprotocol# NOTE 2: The protocol defined by the present document may be combined with other profiles to request additional features or functionality provided by the SCASC as long as these profiles do not conflict with the requirements specified in the present document. The message for requesting the creation of AdES signature(s) to the SCASC may contain other components for requesting additional features. Clause 7.5 lists some of these optional components and contain references to clauses that specify semantic requirements for each component. This message includes the following components. Table 36 Ref. Component for Presence 7.2 asynchronous/synchronous operation mode selection O 7.3 identification of the request O 7.4 credential authorization M 7.5 defining optional data to be returned O 7.6 defining the validity period for asynchronous requests O 7.7 service authentication O 7.8 identifying signature credentials C 7.9 language selection O 7.10 contents from certificate info to be returned O 7.11 managing digital signatures transactions O 7.12 service policy selection O 7.13 signature creation policy selection O 7.14 optional signature attributes/properties selection O 7.15 protocol identifier M 7.16 requesting specific signature formats O 7.18 specifying response URL O 7.19 submitting document(s) or hash(es) to be signed M The component for identifying signature credential may not be included in the message if there is only one signing credential for the user which has been previously authenticated. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 53
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.2.1.2 JSON related component
|
The method signatures/signDoc shall be invoked in order to request the signature of one or more documents or document representations. This method calculate the signature of the documents or document representations provided in input. The elements to request the signature of a document or a document representation shall be the set of required and optional parameters, specified in clause 8.2.1.1, to invoke the document signature by means of the signatures/signDoc method. Processing model The server shall process the components received with the signatures/signDoc in order to calculate the remote digital signature of one or multiple document(s) or SDR(s) as indicated in the clause 8.2.1.1 of the present document.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.2.1.3 XML related component
|
The element that shall be the main component for requesting the creation of AdES signature(s) shall be the root element of the message dss:SignRequest as specified in OASIS DSS-v2.0 [2]. Processing model The server shall process the components in the dss:SignRequest as indicated in the corresponding clauses of OASIS DSS-v2.0 [2]. The server shall process each child of the dss:OptionalInputs and dss:InputDocuments components as indicated in the corresponding clause of the present document if the child is not specified in any of the referenced OASIS documents. Otherwise, the server shall follow the processing model defined in the corresponding OASIS document.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.2.2 Response message (B)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.2.2.1 Component for responding to AdES signatures creation requests
|
The AdES signature creation response message resulting from one request of AdES signatures creation, shall include the component for notifying the global result of the signature operation requested by the client application. The AdES signature creation response message may include one or more signed document or signature elements as defined in clause 7.21. This message includes the following components. Table 37 Ref Component for Presence 7.21 returning signed documents or signatures O 7.22 returning signing certificate information O 7.24 notifying operation result(s) M 7.25 service policy identification O 7.26 response identification C 7.27 signature creation policy identification O The response identification may be included in the response message. The response identification shall be included in the response message if one of the following conditions occurs: 1) The AdES signatures creation request includes the component indicating an asynchronous operation mode to the SCASC, as specified in clause 7.2. 2) The SCASC chooses to process the request in asynchronous mode. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 54
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.2.2.2 JSON related component
|
The element to respond to the signature of the document(s) request shall be the set of components as indicated in the clause 8.2.2.1.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.2.2.3 XML related component
|
The element that shall be the main component for responding to the creation of AdES signature(s) request shall be the root element of the message dss2:SignResponse as specified in OASIS DSS-v2.0 [2].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.3 DSVs creation messages
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.3.1 Request message (C)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.3.1.1 Component for requesting DSVs creation
|
In this scenario the SCASC or an application in the signer's environment prepares the DTBSR(s) that are sent to the SSASC along with other information required to compute the signature. The message for requesting the creation of DSVs to an SSASC shall contain components for: 1) Submitting the DTBSRs. NOTE 1: The message may contain one or more data to be signed representations for DSVs creation. A DSV will be created for each of these input components. 2) Providing credential authorization in the form of signature activation data. 3) Identifying one or more protocols and/or profiles with which the request message is compliant. The first one of such components shall have the following URI as value, identifying the request message as one that has been built using the "digital signature value creation" protocol specified in the present document: - http://uri.etsi.org/19432/v1.1.1/dsvcreationprotocol# NOTE 2: The protocol defined by the present document may be combined with other profiles to request additional features or functionality provided by the SSASC as long as these profiles do not conflict with the requirements specified in the present document. The SSASC creates the digital signature value(s) using the signer's private key held on the SCDev and returns the outcome(s) of the signature operation and information to retrieve DSVs. The message for requesting the creation of DSVs to the SSASC may contain other components for requesting additional features. Clause 7.5 lists some of these optional components and contain references to clauses that specify semantic requirements for each component. This message includes the following components. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 55 Table 38 Ref. Component for Presence 7.2 asynchronous/synchronous operation mode selection O 7.3 identification of the request O 7.4 credential authorization M 7.5 defining optional data to be returned O 7.6 defining the validity period for asynchronous requests O 7.7 service authentication O 7.8 identifying signature credentials C 7.9 language selection O 7.10 contents from certificate info to be returned O 7.11 managing digital signatures transactions O 7.12 service policy selection O 7.13 signature creation policy selection O 7.15 protocol identifier M 7.18 specifying response URL O 7.19 submitting hash(es) to be signed M The component for identifying signature credential may not be included in the message if there is only one signing credential for the user which has been previously authenticated.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.3.1.2 JSON related component
|
The element to request the signature on a DTBSR shall be the set of required parameters to invoke the signature by means of the signatures/signHash method as specified in CSC standard [1]. The signature creation policy element may be used in order to specify the signature algorithm and eventual signature algorithm parameters, alternatively to the parameters signAlgo and signAlgoParams defined in CSC standard [1]. Processing model The server shall process the components as indicated in the signatures/signHash description of the CSC standard [1]. The server shall process each component as indicated in the clause 8.3.1.1 of the present document if the child is not specified in the signatures/signHash description of the CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.3.1.3 XML related component
|
The element for requesting the hash signature(s) shall be the root element of the message dss2:SignRequest. Processing model The server shall process the components inherited from dsb:RequestBaseType as indicated in the clause (Processing for XML Signature) in particular in the variant for <DocumentHash> of OASIS DSS-v2.0 [2].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.3.2 Response message (D)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.3.2.1 Component for responding to DSVs creation requests
|
The DSVs signature creation response message resulting from one request of DSVs creation, shall include the component for notifying the global result of the signature operation requested by the client application. The DSVs creation response message may include one or more DSV elements as defined in clause 7.29. This message includes the following components. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 56 Table 39 Ref Component for Presence 7.22 returning signing certificate information O 7.24 notifying operation result(s) M 7.25 service policy identification O 7.26 response identification C 7.27 signature creation policy identification O 7.29 returning DSV O The response identification may be included in the response message. The response identification shall be included in the response message if one of the following conditions occurs: 1) The DSVs creation request includes the component indicating an asynchronous operation mode to the SCASC, as specified in clause 7.2. 2) The SSASC chooses to process the request in asynchronous mode.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.3.2.2 JSON related component
|
The response to the hash(es) signature request shall consist of the set of parameters returned in the response of the signatures/signHash method as specified in CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.3.2.3 XML related component
|
The element to respond to the DTBS(s) signature request shall be the dss2:SignResponse root element as indicated in the clause 8.5.1 and in OASIS DSS-v2.0 [2] specifications.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.4 Messages for asynchronous processing (E)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.4.1 Component for managing pending-requests
|
This component shall manage the messages for requesting to the SCS to return the responses corresponding to previously sent (initial) signatures or DSVs creation requests, defined in clauses 8.2.1 and 8.3.1, when processed in asynchronous mode by the SCS itself. Requests of this type are named pending-requests hereinafter. In asynchronous processing one client application sends an initial signatures or DSVs creation request to the server. The initial request may contain, among other things, a component by which an asynchronous operation mode is requested to the SCS, as specified in clause 7.2 and a request identifier generated by the client application, as specified in clause 7.3. The server can return a response indicating that the signature creation request has been accepted but it has not yet been completed, either because the client application has requested an asynchronous operation mode to the SCS or because the SCS has chosen to perform the requested operation in asynchronous mode. Within this initial response, the SCS shall convey a response identifier, as specified in clause 7.26. If the initial request contains the request identifier, both the client application and the SCS can correlate this response identifier to the initial request identifier. Under this processing model the client application, after the initial request, can send a pending-request to the SCS. This pending-request shall include in the component for request identification, as defined in clause 7.3, the value of the response identifier previously returned by the SCS in its response to the initial signature creation request. This response identifier value allows the SCS to correlate this pending-request to the initial signature creation request. The SCS shall return the signature creation result or again an indication of "not yet finished". If the latter is the case, the client application can send subsequent requests until the SCS returns a response with the signature creation result. The pending-requests message shall contain components for: 1) Identifying the request as a pending-request associated to an initial signatures or DSVs creation request. The component specified in clause 7.3 shall be used to include the response identifier identifying the pending- request. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 57 2) Identifying one or more protocols and/or profiles with which the pending-request message is compliant. The first one of such components shall have the following URI as value, identifying the pending-request message as one that has been built using the "asynchronous processing" protocol specified in the present document: - http://uri.etsi.org/19432/v1.1.1/asynchronousprotocol# NOTE: The protocol defined by the present document may be combined with other profiles to request additional features or functionality provided by the SCS as long as these profiles do not conflict with the requirements specified in the present document. The response to a pending-request has the format of the response to the initial signatures or DSVs creation request. A pending-request message includes the following components. Table 40 Ref Component for Presence 7.3 identification of the request/polling signature results M 7.7 service authentication O 7.9 language selection O 7.15 protocol identifier M
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.4.2 JSON related component
|
The element that shall indicate to the SCS that the client is requesting the response corresponding to a previously sent (initial) request (as part of an asynchronous protocol) shall be the set of required and optional parameters defined in clause 8.4.1 to invoke the signatures/signPolling method. Processing model The server shall process each component as indicated in the clause 8.4.1. The server shall check the completion of the operations related to the request identified by the attribute requestID and respond accordingly returning the generated DSV(s) or signed document(s) or signature(s) or the indication that the operations have not yet finished or an error code (for example because the request cannot be completed or because the time allowed for requesting the results has expired).
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.4.3 XML related component
|
The element that shall indicate to the SCS that the client is requesting the response corresponding to a previously sent (initial) request (as part of an asynchronous protocol) shall be the dss2:PendingRequest element as specified in OASIS DSS-v2.0 [2].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.5 Signing certificates list messages
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.5.1 Request message (F)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.5.1.1 Component for requesting signing certificates list
|
The message for requesting the list of the signing certificates of a signer shall contain the component for: 1) Identifying one or more protocols and/or profiles with which the request message is compliant. The first one of such components shall have the following URI as value, identifying the request message as one that has been built using the "signing certificates list" protocol specified in the present document: - http://uri.etsi.org/19432/v1.1.1/certificateslistprotocol# NOTE: The protocol defined by the present document may be combined with other profiles to request additional features or functionality provided by the SCS as long as these profiles do not conflict with the requirements specified in the present document. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 58 A signer may have one or multiple credentials associated within a single signer identifier. This message includes the following components. Table 41 Ref Component for Presence 7.3 identification of the request O 7.7 service authentication O 7.9 language selection O 7.10 contents from certificate chain to be returned O 7.15 protocol identifier M 7.17 signer identification C The component for the signer identification may not be included in the message if it is already implicit in the service authentication performed.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.5.1.2 JSON related component
|
The element to retrieve credentials shall be the set of parameters required by the credentials/list method as specified in CSC standard [1]. Processing model The server shall process the components as indicated in the credentials/list description of the CSC standard [1]. The server shall process each component as indicated in the clause 8.5.1.1 of the present document if the child is not specified in any of the referenced CSC standard [1]. Otherwise, the server shall follow the processing model defined in the corresponding CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.5.1.3 XML related component
|
The element that shall be the main component for requesting a signing certificates list shall be the root element of the message etsisig:InformationRequest. The etsisig:InformationRequest element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2. The etsisig:SignerIdentity, child element of the etsisig:OptionalInputs element shall be set in order to identify the signer for which the list of the signing credentials is being requested. Processing model The server shall process the components inherited from the etsisig:SignerIdentity element in order to retrieve and return the list of credentials associated with the user identifier.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.5.2 Response message (G)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.5.2.1 Component for responding to certificates list requests
|
The certificates list response message resulting from one request of certificates list, shall include the component for notifying the global result of the operation requested by the client application. The certificates list creation response message may include one or more certificates elements as defined in clause 7.23. This message includes the following components. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 59 Table 42 Ref Component for Presence 7.23 returning the list of the signing certificate(s) O 7.24 notifying operation result(s) M The SCS shall return an error in the case of a request to obtain the list of certificates associated to a signer other than the one authenticated to the service.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.5.2.2 JSON related component
|
The response to retrieve user's credentials list request shall consist of the set of results specified in clause 8.5.2.1 as defined in clauses 7.23.2 and 7.24.2.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.5.2.3 XML related component
|
The element that shall be the main component for responding with signing certificates list shall be the root element of the message etsisig:InformationResponse. The etsisig:InformationResponse element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2. The ds:KeyInfo, child element of the etsisig:OptionalOutputs element shall return the requested signing certificates list.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.6 Credential information retrieval messages
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.6.1 Request message (H)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.6.1.1 Component for requesting credential information
|
The message for requesting information about a signing credential to the SCS shall contain components for: 1) Identifying the signing credential. 2) Identifying one or more protocols and/or profiles with which the request message is compliant. The first one of such components shall have the following URI as value, identifying the request message as one that has been built using the "credential information" protocol specified in the present document: - http://uri.etsi.org/19432/v1.1.1/credentialinfoprotocol# NOTE: The protocol defined by the present document may be combined with other profiles to request additional features or functionality provided by the SSASC as long as these profiles do not conflict with the requirements specified in the present document. The message for requesting information about a signing credential to the SCS may contain other components for requesting additional features. Clause 7.5 lists some of these optional components and contain references to clauses that specify semantic requirements for each component. This message includes the following components. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 60 Table 43 Ref Component for Presence 7.3 identification of the request O 7.5 defining optional data to be returned O 7.7 service authentication O 7.8 identifying signature credentials C 7.9 language selection O 7.10 contents from certificate info to be returned O 7.15 protocol identifier M The component for identifying signature credential may not be included in the message if there is only one signing credential for the user which has been previously authenticated.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.