Sample
github.com/golang-jwt/jwt/v5 v5.3.1: Validate single and multiple token audiences using WithAudience, WithAllAudiences, and ClaimStrings in jwt/v5
Verified sample for golang github.com/golang-jwt/jwt/v5 v5.3.1: Validate single and multiple token audiences using WithAudience, WithAllAudiences, and…
sha256:a5bbd16d6ea67b8a7eebbb367ba078aef91a7eb164022f08bec050e926dd4e89
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
go linux x64 go go go
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-17 |
| go 1.26 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-18 |
Case
HOW- Goal
- Validate single and multiple token audiences using WithAudience, WithAllAudiences, and ClaimStrings in jwt/v5
- Packages
- Symbols
-
- jwt.WithAudience
- jwt.WithAllAudiences
- jwt.ClaimStrings
- jwt.ParseWithClaims
- Environment
- go
- Created
- 2026-08-17T20:27:29Z
Contract
- jwt.WithAudience matches when any specified audience is present in the token aud claim, whereas jwt.WithAllAudiences requires all specified audiences to be present.
- assert jwt.ClaimStrings deserializes aud claims formatted as either a single JSON string or a JSON array of strings
- assert audience mismatch produces jwt.ErrTokenInvalidAudience while an omitted aud claim produces jwt.ErrTokenRequiredClaimMissing when audience validation is active
Files
- NOTES.md
- audience_test.go
- csx.json
- go.mod
- go.sum