Design Goal and Practical Use of Tenant ID

[jeevan0920]

Current Implementation

Both provisioning and verification APIs use hardcoded tenantID = "0":

// provisioning/api/handler.go:38-39
var (
    tenantID = "0"
)

// verification/api/handler.go:19-21 
var (
    tenantID = "0"
)

Questions

1. What is the design goal of tenant ID?
2. What are the practical use cases for tenant ID?
3. Is the hardcoded "0" intentional or a placeholder?

ARM CCA Context

The ARM CCA store handler uses tenant ID in lookup keys: ARM_CCA://{tenantID}/{implID}/{instID}, but the APIs always pass "0"

Could you clarify the intended design and practical use of tenant ID specifically for ARM CCA attestation schemes?

[setrofim]

The goal is to support multi-tenancy in the future. I.e. multiple orthogonal organisations sharing the same deployment of Veraison services. Each such organisation would have its own tenant ID that all entries in the store are "namespaced" under; that way, conflicts between organisations are not possible.

Multi-tenancy is not currently implemented, hence the tanant ID is always 0.