tegwick
74b35b6107
All checks were successful
Build and Publish Container Image / build-and-push (push) Successful in 34s
serviceSubject and roles are read only on the client_credentials path. On a browser client they are accepted and then ignored, since subject and roles come from the directory user -- so a registration that looks effective fails later as a downstream rejection rather than as a registration defect. tokenLifetime was already rejected this way, so the rule existed and was incomplete. Nothing in dev-config, the example fixture or the live deployment sets either field on a browser client, checked against all three rather than assumed, so this breaks no existing configuration. tenant is deliberately excluded, and a test pins that: a browser client may declare one, and humanTenant resolves it against the directory, refusing issuance when they disagree (KEY-WP-0013-T05). An earlier version of this change rejected tenant too and would have made that feature unusable. It started from T05's blocker paragraph, which was accurate when written and already fixed by the time this task began -- blocker prose ages faster than the code it describes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NV9oijZukGyGbRQGGKnK4P Assistant: claude-code Assistant-Model: opus Assistant-Process: 713576@bnt-lap001 Assistant-Session: 384c511d-9bce-4cb8-a676-2aef6c0c8df6 |
||
|---|---|---|
| .. | ||
| cmd | ||
| internal | ||
| tests | ||
| go.mod | ||
| go.sum | ||
| Makefile | ||