novox/mesh-controller
3
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity

The bus account has JetStream, and the control plane's client has its own inbox #105

Merged
jschoubben merged 1 commits from fix/the-bus-account-has-jetstream into main 2026-09-27 23:40:39 +00:00
Conversation 0 Commits 1 Files Changed 4
+18 -2
jschoubben commented 2026-09-27 23:40:32 +00:00
Owner
Copy Link
Copy Source

Two refusals the first live connections met. A user in the MESH account was told "JetStream not enabled for account" the first time it bound a consumer: with accounts defined, JetStream is enabled per account, not only globally — the account's setting, which the mesh owns, not the server's block, which it does not (the users-only test now says exactly that). And the control plane's client used a random inbox prefix where it is granted exactly _INBOX.<its user>.>, so the server's first answer could not reach it. The prefix now follows from the user in the URL, for every principal that dials that way.

Two refusals the first live connections met. A user in the MESH account was told "JetStream not enabled for account" the first time it bound a consumer: with accounts defined, JetStream is enabled per account, not only globally — the account's setting, which the mesh owns, not the server's block, which it does not (the users-only test now says exactly that). And the control plane's client used a random inbox prefix where it is granted exactly `_INBOX.<its user>.>`, so the server's first answer could not reach it. The prefix now follows from the user in the URL, for every principal that dials that way.
jschoubben added 1 commit 2026-09-27 23:40:32 +00:00
The bus account has JetStream, and the control plane's client has its own inbox 70341cfbc7 
Two refusals the first live connections met. A user in the MESH account was told
"JetStream not enabled for account" the first time it bound a consumer: with
accounts defined, JetStream is enabled per account, not only globally — the
account's setting, which the mesh owns, not the server's block, which it does not.
And the control plane's client used a random inbox prefix where it is granted
exactly _INBOX.<its user>.>, so the server's first answer could not reach it. The
prefix now follows from the user in the URL, for every principal that dials so.
jschoubben merged commit e2ee0dfe98 into main 2026-09-27 23:40:39 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
jschoubben miel.truyen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#105