Add Multi-Tenant Role Validation and Index Modification for Unique Role Names per Tenant #783
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.
Branch Name
feature/multi-tenant-role-validation
Pull Request Description
This pull request introduces the following changes:
Custom Multi-Tenant Role Validator:
MultiTenantRoleValidator
to enforce unique role names per tenant.Replace Default Role Validator:
MultiTenantRoleValidator
in the service collection to replace the defaultRoleValidator<ApplicationRole>
.Index Modification:
ApplicationRole
entity to enforce a unique constraint on the combination ofName
andTenantId
.These changes address the issue of role name collisions in multi-tenant scenarios and provide a consistent solution both at the application and database levels to maintain role uniqueness within each tenant.