You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Aias00 (via GitHub)" <gi...@apache.org> on 2026/10/18 16:53:38 UTC
[I] [Enhancement] Propose a payload-bound MCP signing revision and rollout [rocketmq-dashboard]
Aias00 opened a new issue, #6956:
URL: https://github.com/apache/rocketmq-dashboard/issues/6956
## Requested enhancement
Decide whether a future MCP authentication revision should bind exact request-body bytes and a freshness identifier in addition to the existing method, request target, instance, timestamp and access key.
The current implementation explicitly does not authenticate the body (`rmqctl/internal/studio/auth.go`, `McpAuthenticator.canonicalRequest`), and relies on trusted transport for message integrity. A captured valid authentication header is consequently not a proof of one specific body. This is a proposed stronger protocol guarantee, with its transport assumptions stated; it is not a claim of unauthenticated access over properly secured HTTPS.
## Reviewable proposal
- Keep documenting the current wire format in the existing #5530 / #6028 work.
- Specify a separate revision with SHA-256 of the exact transmitted body bytes (no JSON reserialization), signed method/target/instance/timestamp/nonce and a clear size budget.
- Define the replay-store and retry contract before selecting a nonce mechanism. Reconnect and network retries need fresh authentication; preventing protocol replays and promising exactly-once business execution are different guarantees.
- Agree the client/server rollout, old-client behavior and downgrade policy before runtime changes.
- Keep mutation confirmation-token single-use work in #5452 and hosted human approval in #6027 separate.
A design-only draft will describe alternatives, failure cases and required conformance tests. No runtime format is changed before maintainers agree the compatibility policy.
Baseline: `rocketmq-studio@c34535db0`. No open PR implementing a body-bound authentication revision was found.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Enhancement] Propose a payload-bound MCP signing revision and rollout [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #6956: [Enhancement] Propose a payload-bound MCP signing revision and rollout
URL: https://github.com/apache/rocketmq-dashboard/issues/6956
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Enhancement] Propose a payload-bound MCP signing revision and rollout [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #6956:
URL: https://github.com/apache/rocketmq-dashboard/issues/6956#issuecomment-6405393469
This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org