Say how every operation is authenticated

The document defined bearerAuth and cookieAuth and referenced neither,
so the schemes were decoration: a client generated from the contract
wires no credential and reads the whole surface as open.

The default now offers the two as alternatives, and the ten operations
reachable before a credential exists opt out with an empty array. The
opt-out list is derived from what each handler accepts, not from the
proxy's public-path list — /api/ingest/medication is on that list and
requires a Bearer token, so reading it as the answer would publish an
authenticated route as open. Writing the list from the proxy is exactly
the mistake the guard caught: /api/auth/oidc/callback went on it and is
not published at all.
This commit is contained in:
Marc-André Bombeck committed 2026-08-22 15:03:28 +02:00
1 parent 50b483d8d1
commit 965d41f1ed
6 files changed
+25228 -1142

No files matched your search

+25162 -1140
View File
File diff suppressed because it is too large. Load diff