SPIFFE/SPIRE compatibility for workload identity
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
- Domain
- authentication, security
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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from public/wicket
-
Don't break the machines: node health alerts, admission control, reserved headroom, volume lifecycle, collection trackingPossibly taken @public claimed this today. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement parked
Difficulty 5/5 Over a week Newbie friendliness 12/100
public/wicket#371 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
Windowed egress caps and standard OTLP decision records (from AgentCore, Strands Box and Dogwood)Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yantrikos/yantrik-os#1272 ·
Maintainers usually reply within 1 day
-
crate: spate-kafka priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·