Commit d88bfe5
committed
fix: pass CHALLENGE_UUID env var for broker authentication
The JWT token for broker auth is generated with the challenge UUID,
but CHALLENGE_ID was set to the human-readable name (e.g., 'term-challenge').
This caused a mismatch error when challenges tried to create containers.
Now we pass both:
- CHALLENGE_ID: Human-readable name (for logging, events)
- CHALLENGE_UUID: UUID that matches JWT token (for broker auth)
WsContainerClient.from_env() now prefers CHALLENGE_UUID over CHALLENGE_ID.1 parent 58c8618 commit d88bfe5
File tree
2 files changed
+7
-3
lines changed- crates
- challenge-orchestrator/src
- secure-container-runtime/src
2 files changed
+7
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
520 | 520 | | |
521 | 521 | | |
522 | 522 | | |
| 523 | + | |
| 524 | + | |
523 | 525 | | |
524 | 526 | | |
525 | 527 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
31 | 31 | | |
32 | 32 | | |
33 | 33 | | |
34 | | - | |
| 34 | + | |
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
38 | | - | |
39 | | - | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
40 | 42 | | |
41 | 43 | | |
42 | 44 | | |
| |||
0 commit comments