Egothor/ZeroEcho
2
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects 1 Releases 4 Wiki Activity

Define a formal provider configuration catalogue for framework and crypto providers #14

New Issue
Closed
opened 2026-03-24 18:06:05 +01:00 by galambos · 1 comment
galambos commented 2026-03-24 18:06:05 +01:00
Owner
Copy Link

Provider classes such as BcX509CredentialFrameworkProvider currently expose no supported keys, and its allocation is intentionally minimal.

Why this matters

As the system grows toward profiles, ACME, remote signing, and approval workflows, provider configuration must become explicit, reviewable, and discoverable rather than implicit.

Acceptance criteria

  • Define configuration keys for framework providers, crypto workflow providers, and related components where needed.
  • Keep keys stable and documented.
  • Validate unknown/unsupported keys consistently.
  • Ensure the bootstrap logs only keys, not sensitive values.
Provider classes such as BcX509CredentialFrameworkProvider currently expose no supported keys, and its allocation is intentionally minimal. ## Why this matters As the system grows toward profiles, ACME, remote signing, and approval workflows, provider configuration must become explicit, reviewable, and discoverable rather than implicit. ## Acceptance criteria - Define configuration keys for framework providers, crypto workflow providers, and related components where needed. - Keep keys stable and documented. - Validate unknown/unsupported keys consistently. - Ensure the bootstrap logs only keys, not sensitive values.
galambos added this to the PKI Foundation Hardening and Regulated Operations Roadmap project 2026-03-24 18:56:06 +01:00
galambos self-assigned this 2026-04-05 22:23:34 +02:00
galambos commented 2026-08-11 22:18:13 +02:00
Author
Owner
Copy Link

ConfigurableProvider defines supported-key discovery and unknown-key handling. In-tree providers publish and validate their keys and log key names without values.

ConfigurableProvider defines supported-key discovery and unknown-key handling. In-tree providers publish and validate their keys and log key names without values.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project PKI Foundation Hardening and Regulated Operations Roadmap
Assignees
Clear assignees
galambos gitea-ci
No Assignees galambos
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Egothor/ZeroEcho#14
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?