Skip to content

fix(e2e): adopt the verifier's oauth.jwt.mode enum #8

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
y1o1 merged 1 commit into from
Aug 27, 2026
Merged

fix(e2e): adopt the verifier's oauth.jwt.mode enum #8

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
8 changes: 5 additions & 3 deletions tests/abac/application.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}
}
}

Expand Down
Loading