feat: signature certificate profiles#87
Open
peppelinux wants to merge 2 commits into
Open
Conversation
peppelinux
changed the title
MartinRobomaze
approved these changes
Mar 16, 2026
marosrbm
approved these changes
Mar 16, 2026
andmoro
requested changes
Jun 19, 2026
| ### PID Provider (legal person) | ||
|
|
||
| ``` | ||
| Subject: C=DE, O=Bundesdruckerei GmbH, organizationIdentifier=NTRDE-HRB12345, CN=German PID Issuer Service |
Collaborator
There was a problem hiding this comment.
ETSI TS 119 412-6 defines the certificates profiles on top of these already defined by previous ETSI TS 119 412. These should at least be cited.
X509 certificates generally need the required version, ... parameters, if we decide to use this X509 profile, then the examples below are inconsistent.
Contributor
Author
There was a problem hiding this comment.
May I ask you to add the version and further details improving the examples given?
|
|
||
| **Attestation Providers (EAA, QEAA, PSBEAA):** Certificates used to sign attestations. If OCSP/CRL is used for attestation revocation, the OCSP responder cert or CRL must be issued/signed by the provider's sign/seal certificate. | ||
|
|
||
| ### UC-03: Wallet Provider Onboarding |
Collaborator
There was a problem hiding this comment.
This section doesn't add much wrt the previous (OID).
andmoro
reviewed
Jun 19, 2026
| ``` | ||
| Subject: C=DE, O=Bundesdruckerei GmbH, organizationIdentifier=NTRDE-HRB12345, CN=German PID Issuer Service | ||
| Extensions: | ||
| keyUsage = digitalSignature |
Collaborator
There was a problem hiding this comment.
AS per ETSI EN 319 412-2 § 4.3.2 Key usage should be set to Type A, i.e., nonRepudiation.
Co-authored-by: Andrea Moro <anmoro@fbk.eu>
peppelinux
changed the title
cklugow
approved these changes
Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ETSI certificate profiles relevant to PID, Wallet, EAA, QEAA, and PSBEAA providers, clarifying their requirements and mapping them to use cases. The main changes include the addition of detailed markdown files summarizing the ETSI EN 319 412-2 and EN 319 412-3 standards, a new overview for TS 119 412-6, and updates to the documentation index.
New ETSI certificate profile documentation:
ETSI_EN_319_412-2_V2.4.1.mdsummarizing certificate profile requirements for natural persons, including subject field requirements, key usage types, CRL/AIA extensions, and EU Qualified Certificate specifics.ETSI_EN_319_412-3_V1.3.1.mdsummarizing certificate profile requirements for legal persons, including subject and key usage requirements, and how these profiles amend or build on EN 319 412-2.