On the embedded broker a container logs in as its task with its run credential and reaches only its own subjects. An external broker has no such hook, so in external mode containers still receive the broker's own token, which reaches every subject; archied reports this as the nats_credential_scope health issue. Done when an external broker delegates container logins to archied through NATS auth callout and grants the same per-task subjects, and the health issue is gone.
Imported from beads archie-core-ei1i · GitHub #1376 · type task · priority P3 · created 2026-10-04
On the embedded broker a container logs in as its task with its run credential and reaches only its own subjects. An external broker has no such hook, so in external mode containers still receive the broker's own token, which reaches every subject; archied reports this as the nats_credential_scope health issue. Done when an external broker delegates container logins to archied through NATS auth callout and grants the same per-task subjects, and the health issue is gone.
---
_Imported from beads `archie-core-ei1i` · GitHub #1376 · type task · priority P3 · created 2026-10-04_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On the embedded broker a container logs in as its task with its run credential and reaches only its own subjects. An external broker has no such hook, so in external mode containers still receive the broker's own token, which reaches every subject; archied reports this as the nats_credential_scope health issue. Done when an external broker delegates container logins to archied through NATS auth callout and grants the same per-task subjects, and the health issue is gone.
Imported from beads
archie-core-ei1i· GitHub #1376 · type task · priority P3 · created 2026-10-04