casework serve: OIDC discovery against a loopback http issuer fails without naming the reason

Open Beginner friendly
#1,005 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
authentication, backend, security

Research direction

Start by reproducing the failure with casework serve using an OIDC discovery default and a loopback http://127.0.0.1:<port> issuer, then trace the startup OIDC initialization entry point. Compare it with the static jwksSource configuration written by caseworkctl dev. Done means the startup error identifies whether the issuer scheme, host, or discovery document caused the failure.

Written by the indexing model from the issue text.

Description

agent-ready area:casework bug criticality:p3

Found while writing the public tutorial Review BReg changes in Casework.

What Happened

casework serve with authentication.oidc.jwksSource left at its discovery default, pointed at a Registry Mint on http://127.0.0.1:<port>, failed at startup with:

the OIDC issuer could not be initialized

The message does not say whether the issuer was refused for its scheme, its host, or an unreachable discovery document. The working configuration is a static JWKS reference:

jwksSource:
  kind: static
  documentRef: secret:file/mint-jwks

which is what caseworkctl dev writes.

Expected Behavior

The startup failure names the reason (for example "discovery requires an https issuer; loopback http issuers need a static jwksSource"). Whether loopback http discovery should be allowed at all is a separate call; the message is the bug.

Environment

Registry Stack 0.30.0 release binaries, macOS.

Triage: later.

Dominant language
Rust
Stars
2
Forks
0
Avg merge
3h 45m
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from registrystack/registry-stack

All issues in registrystack/registry-stack

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.