Skip to content

Test unreachable JWKS URIs #1099

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jviotti merged 1 commit into from
Jul 2, 2026
Merged

Test unreachable JWKS URIs #1099

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions enterprise/e2e/auth-path/hurl/jwt.all.hurl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,3 +124,28 @@ POST {{base}}/registry/self/v1/api/schemas/evaluate/self/v1/schemas/api/error
HTTP 200
[Asserts]
jsonpath "$.valid" == true

# The unreachable policy has no explicit key set, so its issuer's discovery
# endpoint is fetched and fails, denying rather than admitting on the failure
GET {{base}}/registry/unreachable/record.json
Authorization: Bearer {{access_token}}
HTTP 401
Content-Type: application/problem+json
Cache-Control: no-store
WWW-Authenticate: Bearer realm="registry"
Link: </registry/self/v1/schemas/api/error>; rel="describedby"
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Link, ETag
[Captures]
discovery_failure_denied: body
[Asserts]
jsonpath "$.type" == "urn:sourcemeta:one:authentication-required"
jsonpath "$.status" == 401

POST {{base}}/registry/self/v1/api/schemas/evaluate/self/v1/schemas/api/error
```
{{discovery_failure_denied}}
```
HTTP 200
[Asserts]
jsonpath "$.valid" == true
11 changes: 10 additions & 1 deletion enterprise/e2e/auth-path/one.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,12 +35,21 @@
"audience": "https://schemas.example.com",
"jwksUri": "http://hydra:4444/.well-known/jwks.json",
"algorithms": [ "RS256" ]
},
{
"type": "jwt",
"name": "unreachable",
"paths": [ "/unreachable" ],
"issuer": "https://unreachable.example.invalid",

@augmentcode augmentcode Bot Jul 2, 2026 •
edited
Loading

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This issuer is intentionally unreachable, but it will still trigger a real OIDC discovery HTTP fetch on the first request to /unreachable (and discovery failures aren’t cached), so this can add up to the full JWKS fetcher timeout per request and potentially slow/flake the e2e run.

Severity: low

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

"audience": "https://schemas.example.com",
"algorithms": [ "RS256" ]
}
],
"contents": {
"public": { "path": "./schemas/public" },
"private": { "path": "./schemas/private" },
"machine": { "path": "./schemas/machine" },
"foreign": { "path": "./schemas/foreign" }
"foreign": { "path": "./schemas/foreign" },
"unreachable": { "path": "./schemas/unreachable" }
}
}
11 changes: 11 additions & 0 deletions enterprise/e2e/auth-path/schemas/unreachable/record.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": [ "identifier" ],
"properties": {
"identifier": {
"type": "string"
}
},
"additionalProperties": false
}
Loading