Aegis Multi-Tenancy Enforcer FAQs

Question 1

Why is communityId mandatory in every database query?

Accepted Answer

To ensure total data isolation and prevent users from one community accessing or modifying data belonging to another community, which is a critical security requirement in multi-tenant systems.

Question 2

Where should the communityId be sourced from according to this skill?

Accepted Answer

It must always be extracted from an authenticated JWT token via the controller and passed down to the service layer. Sourcing it from the request body is forbidden as it can be forged by an attacker.

Question 3

Does this skill apply to the Community collection itself?

Accepted Answer

No. The Community collection is the tenant root and queries use the record's primary ID directly for administrative operations, making it the only exception to the communityId filter rule.

Question 4

How does this skill improve MongoDB performance?

Accepted Answer

It enforces a rule that all compound indexes must have communityId as the first field, ensuring that the database can efficiently filter and isolate tenant data during query execution.

Question 5

What is considered a dangerous anti-pattern in this context?

Accepted Answer

Common anti-patterns include performing ID-only lookups without a community filter, making communityId an optional parameter, or trusting tenant IDs provided in the request body.

Aegis Multi-Tenancy Enforcer

主要功能

使用场景

Aegis Multi-Tenancy Enforcer

主要功能

使用场景