Repository navigation
Description
User story
As an ISV integrating Deployment v2 into a multi-tenant service,
I want built-in tenant-aware support for Vault secrets and MPS redirection sessions,
so that I can offer tenants independent configurations, credentials, and device-management sessions with less custom integration work.
Background
Customers are asking for broader multi-tenant support in Deployment v2. The services already support tenant-aware database behavior and allow ISVs to customize ISecretManagerService, but the built-in Vault integration does not yet provide tenant partitions. For example, two tenants creating a profile with the same name can use the same Vault path (RPS #2936). A request for a Google Cloud Secret Manager provider and optional write metadata also illustrates the range of provider integrations ISVs may need (RPS #2945).
MPS already supports short-lived, device-scoped redirection tokens (MPS #527). The feature should carry tenant identity through token issuance and redirection validation, building on the existing device and expiry checks and current tenant comparison.
Feature requests
1. Tenant-aware Vault support in RPS and MPS
Add native support for keeping tenant-owned secrets in separate Vault partitions for both RPS and MPS. Today, secrets are addressed by paths such as profiles/{profileName} and devices/{deviceId}, so tenants using the same resource name can target the same secret path (RPS #2936).
The built-in implementation should use the tenant context already supplied by the ISV integration and apply it consistently when reading, writing, and deleting tenant-owned secrets. Cover the credential-bearing resources in both services, including profiles, certificates/domains, CIRA configurations, wireless configurations, and device credentials. Preserve existing single-tenant behavior and document any required migration or changes to custom ISecretManagerService implementations.
ISVs may continue to provide their own secret-manager implementations for provider-specific needs. The provider request in RPS #2945 is useful context for keeping the interface extensible and compatible with out-of-tree implementations.
2. Tenant-aware MPS redirection tokens
Extend the short-lived device redirection token work from MPS #527 so tenant identity is carried from token issuance through redirection session validation. The session should be tied to the requested device and the tenant associated with that device, while retaining the existing short lifetime and device-scoping behavior.
3. Explain the complete multi-tenancy integration in the docs
Bring the relevant multi-tenancy guidance from the Deployment architecture deep dive into the docs repository, expanding the existing middleware extensibility and secrets management guides as appropriate.
Make it clear that tenant-aware Vault partitions are one part of the feature, not a turnkey multi-tenant deployment. Explain what ISVs must provide and configure to make the full workflow work, including:
- Middleware in both RPS and MPS that derives tenant identity from the ISV's authenticated context and propagates it to service operations.
- Tenant-aware database use and tenant propagation across API, device, and RPC workflows.
- A tenant-aware secret provider or configuration of the built-in Vault partition support, including how
ISecretManagerServicecan be extended or replaced. - Deployment and maintenance of any customized middleware or provider implementation.
Include a clear integration overview and link the middleware, secrets, and multi-tenancy documentation so users can identify both the built-in capabilities and the integration work they own.
Implementation approach
The requests appear sufficiently defined to proceed as feature work. The exact Vault partition mechanism and its compatibility with existing paths can be settled during implementation; use a short design spike only if that choice exposes unresolved tradeoffs around tenant mapping, shared secrets, or migration.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsIn Progress
- StatusShow more project fieldsQ4 2026
Activity
feat(redir): validate redirection tokens
feat(devices): improve KVM connection feedback
feat(devices): improve KVM connection feedback
4 remaining items
feat(redir): scope token issuance to request tenant
refactor(redir): validate redirection tokens (#2721)
feat(redir): scope token issuance to request tenant (#2723)
chore(release): 2.36.0 [skip ci]
chore(release): 4.2.0 [skip ci]
feat(secrets): scope secret store paths to the request tenant
feat(secrets): gate tenant partitioning behind a setting and migrate …
feat(secrets): gate tenant partitioning behind a setting and migrate …
feat(secrets): tenant-scoped secret paths with opt-in startup migration
feat(secrets): tenant-scoped device secret paths with opt-in startup …