Skip to content

docs: Sentry Ed25519 workload identity keys#5181

Open
nelson-parente wants to merge 2 commits into
dapr:v1.18from
nelson-parente:docs/1.18-sentry-ed25519
Open

docs: Sentry Ed25519 workload identity keys#5181
nelson-parente wants to merge 2 commits into
dapr:v1.18from
nelson-parente:docs/1.18-sentry-ed25519

Conversation

@nelson-parente
Copy link
Copy Markdown
Contributor

Summary

  • Documents the Dapr 1.18 change where Sentry switched workload identity X.509 key generation from ECDSA P-256 to Ed25519 (runtime PR dapr/dapr#9598).
  • Covers the positive-side story (what changed, why, rolling upgrade compatibility) as well as FIPS and downgrade constraints.
  • The related injector/operator RSA webhook serving certs change (dapr/dapr#9873) is mentioned for context but tracked separately as gap R5.

Files touched

File Change
daprdocs/content/en/concepts/security-concept.md New "Workload identity key algorithm" subsection under "Secure Dapr to Dapr communication": algorithm comparison table, rationale for Ed25519, explanation of why injector/operator stay RSA, why JWT signing stays RSA-2048, mixed-version upgrade note, FIPS callout (Ed25519 not FIPS-140 approved; BYO-CA is the workaround), downgrade floor alert (1.17.7). Also fixes stale "ECDSA private key" sentence in the same section.
daprdocs/content/en/operations/security/mtls.md New "Workload identity key algorithm" section at the top of the page pointing to the concept page for details. Adds BYO-CA note (supplied issuer key algorithm is what Sentry uses — relevant for FIPS). Fixes stale "ECDSA PEM encoded" in self-hosted BYO-certs prose. Adds inline note on Kubernetes openssl example clarifying RSA keys are also accepted.

Test plan

  • Hugo renders the new alerts and table without errors (hugo serve locally).
  • The {{% ref "security-concept.md#workload-identity-key-algorithm" %}} anchor link resolves.
  • The {{% ref "mtls#bringing-your-own-certificates" %}} link resolves.
  • No broken links (htmltest or equivalent passes).
  • Spot-check prose for accuracy against dapr/dapr#9598 diff.
  • FIPS callout reviewed for accuracy (Ed25519 / Curve25519 is not on FIPS 140-2/-3 approved list).
  • Downgrade floor version (1.17.7) confirmed against dapr/dapr#9904.

Related

  • Runtime PR: dapr/dapr#9598 — Sentry: Use Ed25519 for X.509 certificate key generation
  • Ed25519 PEM-decoder fix (backported to 1.17.7): dapr/dapr#9904
  • Injector/Operator RSA webhook certs (gap R5, separate PR): dapr/dapr#9873

Targets v1.18. Draft pending review.

Sentry switched workload X.509 certificate key generation from ECDSA
P-256 to Ed25519 in Dapr 1.18 (dapr/dapr#9598).

Changes:
- concepts/security-concept.md: add 'Workload identity key algorithm'
  subsection under 'Secure Dapr to Dapr communication'. Covers what
  changed (default: Ed25519 for workload/CA certs, RSA for injector/
  operator webhook serving certs, RSA-2048 for JWT/OIDC unchanged),
  why (smaller keys/sigs, faster ops, cleaner curve design), mixed-
  version rolling-upgrade compatibility, FIPS callout (Ed25519 is not
  FIPS-140 approved; BYO-CA path is the workaround), and downgrade
  floor alert (1.17.7). Also updates stale 'ECDSA private key'
  sentence in the same section.
- operations/security/mtls.md: add 'Workload identity key algorithm'
  section at the top pointing to the concept page. Adds BYO-CA note
  explaining that supplied issuer key algorithm is what Sentry uses.
  Updates stale 'ECDSA PEM encoded' in self-hosted BYO-certs prose.
  Adds inline note on the Kubernetes openssl example clarifying that
  RSA keys are also accepted (relevant for FIPS environments).

Related: dapr/dapr#9873 (injector/operator RSA webhook certs —
tracked separately as gap R5).
Targets v1.18.

Signed-off-by: Nelson Parente <nelson_parente@live.com.pt>
Signed-off-by: Nelson Parente <nelson_parente@live.com.pt>
@nelson-parente nelson-parente marked this pull request as ready for review May 22, 2026 10:04
@nelson-parente nelson-parente requested review from a team as code owners May 22, 2026 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant