Skip to content

fix(e2e): broaden CUSTOM_JWT rejection regex to match service response #1622

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

Closed
notgitika wants to merge 1 commit into from
+2 −1
Closed

fix(e2e): broaden CUSTOM_JWT rejection regex to match service response #1622

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
3 changes: 2 additions & 1 deletion e2e-tests/harness-custom-jwt.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,8 @@ import { afterAll, beforeAll, describe, expect, it } from 'vitest';
const hasAws = hasAwsCredentials();
const canRun = prereqs.npm && prereqs.git && hasAws;
const region = process.env.AWS_REGION ?? 'us-east-1';
const customJWTRejectMsgRegex = /configured for CUSTOM_JWT|[Aa]uthoriz(ation|er).*mismatch|different.*authorization/i;
const customJWTRejectMsgRegex =
/configured for CUSTOM_JWT|[Aa]uthoriz(ation|er).*mismatch|different.*authorization|missing required audience claim/i;

describe.sequential('e2e: harness with CUSTOM_JWT auth', () => {
let testDir: string;
Expand Down
Loading