Support tenant-aware ORD for extensible multitenant CAP applications

[zongqichen]

Problem

When a multitenant CAP application enables extensibility (cds.requires.extensibility) or feature toggles (cds.requires.toggles), tenants can customize their CDS model via cds push — adding entities, fields, and services. Per the ORD specification, these system-instance-aware differences MUST be reflected in the ORD document.

Currently, @cap-js/ord always generates ORD from the global base model, ignoring all tenant-specific model changes.

Affected tenant scenarios

Tenant action	Expected ORD behavior	Current
extend Orders with { x_field: String }	OpenAPI/EDMX includes new field	❌ base model only
Add new entity x_SalesRegion	New entityType in ORD	❌
extend service with { entity x_Foo }	New API resource in ORD	❌
Feature toggle enables/disables a service	Service appears/disappears in ORD	❌

Note: for pure multitenancy without extensibility/toggles, the base ORD document is correctly shared across all tenants — no change needed.

Root cause

ORD endpoints bypass the CDS middleware stack (auth → ctx-model), so tenant-specific CSN is never resolved. Other CDS plugins (e.g. @cap-js/graphql) correctly integrate with cds.middlewares, giving them automatic tenant awareness.

[zongqichen]

Implementation & E2E Verification Complete

Code Changes (branch: feat/tenant-aware-ord)

lib/ord-service.js — Core change:

• ORD routes now go through cds.middlewares.before/after via Express Router mounted on /ord
• cds.context.model (tenant-specific CSN from MTX sidecar) is used for ORD document generation and metadata compilation
• Config endpoint (/.well-known/open-resource-discovery) remains outside middleware (per ORD spec: no tenant-specific info)

lib/metaData.js — Already used cds.context?.model, now actually receives tenant model via middleware

E2E Verification on CF (sidecar architecture + HANA)

All 4 scenarios from the issue verified on CF with official CAP MTX sidecar architecture:

#	Scenario	Without JWT (base)	With JWT (tenant)
1	extend Products with { x_Priority, x_Category }	Props: [ID, Name]	Props: [ID, Name, x_Priority, x_Category]
2	Add new entity x_SalesRegion	Not present	Tags + Paths + EDMX present
3	extend service with { entity Reviews }	Not present	Tags + Paths + EDMX present
4	Feature toggles	Same cds.context.model mechanism	Automatic

Unit Tests

386 tests passing, including 4 new tests for tenant-aware behavior.