From 13041c25580e4118c36fabbac12c8f66b892a129 Mon Sep 17 00:00:00 2001 From: yoshi49535 Date: Thu, 27 Aug 2026 21:14:02 +0900 Subject: [PATCH] fix(e2e): adopt the verifier's oauth.jwt.mode enum auth.policy-verifier#134 replaced oauth.jwt.validate / allowInsecureDecode with mode = "verify" | "insecure-decode" and made the removed keys a boot error. The E2E clones siblings from their default branches, so the abac suite broke the moment that landed. Co-Authored-By: Claude Fable 5 --- tests/abac/application.conf | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/tests/abac/application.conf b/tests/abac/application.conf index 6285a00..3e011a9 100644 --- a/tests/abac/application.conf +++ b/tests/abac/application.conf @@ -10,13 +10,15 @@ http { oauth { jwt { secret = ${?OAUTH_JWT_SECRET} - # RFC 9068 §4 — required by auth.policy-verifier whenever validate = true. + # RFC 9068 §4 — required by auth.policy-verifier whenever mode is "verify". # This file is mounted OVER the template's application.conf, so the # substitutions have to be repeated here or the keys are simply absent. issuer = ${?OAUTH_JWT_ISSUER} audience = ${?OAUTH_JWT_AUDIENCE} - validate = true - validate = ${?OAUTH_JWT_VALIDATE} + # auth.policy-verifier#134 replaced the validate / allowInsecureDecode pair + # with one enum; the verifier now refuses to boot on the removed keys. + mode = "verify" + mode = ${?OAUTH_JWT_MODE} } }