-
Notifications
You must be signed in to change notification settings - Fork 19
ETSI TS 119 432 v1.3.1 (2026-03) - Electronic Signatures and Infrastructures (ESI); Protocols for remote digital signature creation #68
Copy link
Copy link
Open
Labels
Art 5a(23) ICFIntegrity & Core functionalities of EUDI WalletsIntegrity & Core functionalities of EUDI WalletsCIR (EU) 2026/1731Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982Cat: Protocols & InteroperabilityFunctional requirements defining common standards ensuring seamless cross-border interoperability.Functional requirements defining common standards ensuring seamless cross-border interoperability.Cat: Relying PartiesFunctional requirements for relying parties on registration, auth, data requests, and handling.Functional requirements for relying parties on registration, auth, data requests, and handling.Cat: Wallet ProvidersFunctional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Functional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Domain: Cross DomainCommon enablers shared across domains, such as cryptographic primitives, transport security, etc.Common enablers shared across domains, such as cryptographic primitives, transport security, etc.Domain: Trust ServicesSTS underpinning trust infrastructure, including electronic signatures, timestamps, certificatesSTS underpinning trust infrastructure, including electronic signatures, timestamps, certificatesDomain: WalletCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsEssentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialFn: QESFunctional: Qualified Electronic Signature, both for the Wallet and TSPsFunctional: Qualified Electronic Signature, both for the Wallet and TSPsFnRAn STS that specifies Functional RequirementsAn STS that specifies Functional RequirementsgapThis ticket is about a gap identified in our analysis and needs to be scheduledThis ticket is about a gap identified in our analysis and needs to be scheduledsts: needs follow upThe standard needs follow up due to a forthcoming updated versionThe standard needs follow up due to a forthcoming updated versionsts: readyThe standard has a stable version publishedThe standard has a stable version publishedtest specificationSTS entry has linked functional conformance testing activities.STS entry has linked functional conformance testing activities.
Milestone
Description
Metadata
Metadata
Assignees
Labels
Art 5a(23) ICFIntegrity & Core functionalities of EUDI WalletsIntegrity & Core functionalities of EUDI WalletsCIR (EU) 2026/1731Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982Cat: Protocols & InteroperabilityFunctional requirements defining common standards ensuring seamless cross-border interoperability.Functional requirements defining common standards ensuring seamless cross-border interoperability.Cat: Relying PartiesFunctional requirements for relying parties on registration, auth, data requests, and handling.Functional requirements for relying parties on registration, auth, data requests, and handling.Cat: Wallet ProvidersFunctional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Functional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Domain: Cross DomainCommon enablers shared across domains, such as cryptographic primitives, transport security, etc.Common enablers shared across domains, such as cryptographic primitives, transport security, etc.Domain: Trust ServicesSTS underpinning trust infrastructure, including electronic signatures, timestamps, certificatesSTS underpinning trust infrastructure, including electronic signatures, timestamps, certificatesDomain: WalletCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsEssentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialFn: QESFunctional: Qualified Electronic Signature, both for the Wallet and TSPsFunctional: Qualified Electronic Signature, both for the Wallet and TSPsFnRAn STS that specifies Functional RequirementsAn STS that specifies Functional RequirementsgapThis ticket is about a gap identified in our analysis and needs to be scheduledThis ticket is about a gap identified in our analysis and needs to be scheduledsts: needs follow upThe standard needs follow up due to a forthcoming updated versionThe standard needs follow up due to a forthcoming updated versionsts: readyThe standard has a stable version publishedThe standard has a stable version publishedtest specificationSTS entry has linked functional conformance testing activities.STS entry has linked functional conformance testing activities.
Type
Projects
StatusShow more project fields
🏗 In progress
Formal name
ETSI TS 119 432 v1.3.1 (2026-03) - Electronic Signatures and Infrastructures (ESI); Protocols for remote digital signature creation
Overview
The present document specifies protocols and interfaces applicable when the process of creating AdES digital signatures as defined by ETSI EN 319 102-1 and/or digital signature values, as result of Data To Be Signed Representations signatures, is carried out by a distributed solution comprised of two or more systems/services/components.
The present document is limited to remote server signing, i.e. the signing key is held in a remote shared service.
NOTE: Remote signature creation with local signing, i.e. the signing key is held with the signer's personal device but other steps in the signature creation are carried out by means of networked services, is a possible solution but protocols for such architecture are not covered in the present document.
Finally, the present document does not specify any mandatory binding.
As far as it has been possible and suitable, references to constructs of CSC API JSON specifications and OASIS DSS-X XML specifications are specified in the present document. When this has not been possible the present document specifies new components semantically and also syntactically.
The authorized signer's use of its key for signing requires users to provide multiple proofs of their claimed identity before being granted access to the needed set of resources. The present document considers some ways in which the user identity verification process and the user signatures authorization process can be carried out by the service provider.
Work Plan
Current Version
EC Assessment Status
Forthcoming Version
Testing & Conformance
Updates
Alerts
There are no open alerts.
References
None.