SPIFFE/SPIRE compatibility for workload identity

Open
#52 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust

Research direction

Start with design sections §2.1 and §3.2, then read related issues #2, #13, and #32 to understand the current identity and issuance design. The issue does not name implementation files or tests, so trace the identity issuer and relay entry points before estimating the work. Done means a standard SPIFFE library verifies a wicket identity and wicket works with SPIRE as issuer in a test setup.

Written by the indexing model from the issue text.

Description

enhancement

Why. wicket's identity layer is a small SPIFFE-shaped issuer (#2). It shouldn't grow into its own SPIRE.

What.

  • Use SPIFFE formats: JWT-SVIDs (or X.509-SVIDs) with SPIFFE IDs and trust bundles, so standard tooling can verify wicket identities.
  • Put issuance behind an interface, so a real SPIRE deployment can be the issuer: wicket registers each box as a workload entry (as a workload attestor) and the box's relay obtains its SVID.
  • Keep wicket's additions as claims: delegation chain, principal, run, manifest digest.
  • Rotation, revocation and the audit stay as now.

Done when. A standard SPIFFE library verifies a wicket identity, and wicket runs with SPIRE as its issuer in a test setup.

Refs. design §2.1, §3.2; #13, #32.

Dominant language
Rust
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
190

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from public/wicket

All issues in public/wicket

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.