fix(schemas): add user tenantId foreign key constraint #6644
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
We have identified a bug where developers can insert cross-tenant users into an organization using the
POST /organizations/:id?users
API. Previously, there was no constraint to ensure that a user'stenant_id
matches the current organization'stenant_id
.To address this issue, we will add a foreign key constraint for the (tenant_id, user_id) in the
organization_user_relations
table.Testing
test locally
Checklist
.changeset