You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TerraYield need (FedRAMP-target constraint). The full identity broker (#12, S0–S7) gates brokered SSO, but TerraYield cannot expose an unauthenticated read-only MCP surface even for a demo — it is a FedRAMP Moderate-target app and unauthenticated federation surfaces are a compliance non-starter. The current P0 plan ("read-only, no broker dependency") implicitly assumes exactly that.
Acceptance
IONe can hold a static per-peer, per-workspace credential (API key / bearer) and present it on every MCP request to that peer.
Credentials stored encrypted at rest; rotation is a config operation, not a schema change.
TerraYield need (FedRAMP-target constraint). The full identity broker (#12, S0–S7) gates brokered SSO, but TerraYield cannot expose an unauthenticated read-only MCP surface even for a demo — it is a FedRAMP Moderate-target app and unauthenticated federation surfaces are a compliance non-starter. The current P0 plan ("read-only, no broker dependency") implicitly assumes exactly that.
Acceptance
TerraYield already has API-key auth (ty-auth) — with this, its MCP surface rides the existing key infrastructure from day one.