fix(routing): per-recipient checks via the alerts service principal #46

Merged

KofTwentyTwo merged 2 commits from feature/service-principal into develop

2026-10-16 18:33:28 +00:00

Author	SHA1	Message	Date
james.maesandClaude Opus 5.5	b89c95f749	build: QQQ 4.1.0-RC.19 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-16 13:19:08 -05:00
james.maesandClaude Opus 5.5	86b4ca5ff4	fix(routing): per-recipient checks run via the alerts service principal Token-less automated sessions are rejected under OAuth2, so visibility, follower and audience checks never worked there. With the host's alerts principal declared they run on the recipient's behalf through it. Recording/routing bookkeeping stays system so alerting never depends on the IdP. Undeclared: unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-16 08:30:04 -05:00

Author

SHA1

Message

Date

james.maesandClaude Opus 5.5

b89c95f749

build: QQQ 4.1.0-RC.19

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-16 13:19:08 -05:00

james.maesandClaude Opus 5.5

86b4ca5ff4

fix(routing): per-recipient checks run via the alerts service principal

Token-less automated sessions are rejected under OAuth2, so visibility,
follower and audience checks never worked there. With the host's alerts
principal declared they run on the recipient's behalf through it.
Recording/routing bookkeeping stays system so alerting never depends on
the IdP. Undeclared: unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-16 08:30:04 -05:00