Skip to content

test(deps): pin oidc-provider to ^8.5 so the backend tests pass#136

Closed
JohnMcLear wants to merge 1 commit intomainfrom
test/pin-older-oidc-provider
Closed

test(deps): pin oidc-provider to ^8.5 so the backend tests pass#136
JohnMcLear wants to merge 1 commit intomainfrom
test/pin-older-oidc-provider

Conversation

@JohnMcLear
Copy link
Copy Markdown
Member

Backend CI has been failing with 90 login-flow assertions of the form "expected .../auth?... to start with .../interaction/". Root cause: oidc-provider v8.8 changed the /auth endpoint's redirect behaviour — it no longer sends 302/303 → /interaction/ that static/tests/backend/oidc-provider.js relies on. Pin the dev-only dep to ^8.5 to restore CI while a follow-up updates the harness.

oidc-provider v8.8.x changed its /auth redirect behaviour in a way
that doesn't match the test harness in static/tests/backend/oidc-provider.js
(/auth returns a non-redirect status instead of 302/303 → /interaction/,
so the test harness stalls and 90 login-flow assertions fail).

Pin the dev-only dep to ^8.5 for now, which the current harness
supports. A proper follow-up would update the harness to drive whatever
new interaction flow v8.8+ uses.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@JohnMcLear
Copy link
Copy Markdown
Member Author

Pinning to ^8.5.3 didn't change the behaviour — same 90 login-flow assertions still fail. The root cause is in how the harness (static/tests/backend/oidc-provider.js) drives the mock provider's /auth endpoint, not the provider version alone. Leaves this for a proper follow-up that can run the tests locally and step through the interaction flow.

@JohnMcLear JohnMcLear closed this Apr 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant