L3 - Default Environment (Required on creation):
Camunda Automation Platform 7.17.1
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
When deleting a tenant membership using IdentityService#deleteTenantUserMembership or IdentityService#deleteTenantGroupMembership all memberships for the tenant are deleted.
Steps to reproduce (Required on creation):
- Enable Authorization
- Create two groups
- Create a tenant
- Create memberships for each tenant and group combination
- Delete one membership using IdentityService#deleteTenantGroupMembership
Observed Behavior (Required on creation):
All memberships related to the tenant are gone.
Expected behavior (Required on creation):
Only the membership related to the respective group/user and tenant is deleted.
Root Cause (Required on prioritization):
The WHERE condition in the SQL query doesn't restrict the deletion to the respective user or group.
Solution Ideas (Optional):
Use queries that restrict the deletion to a user or group.
Hints (optional):
- The same misbehavior exists for deleting tenant <-> user memberships.
- See PR: https://github.com/camunda/camunda-bpm-platform/pull/1902
This is the controller panel for Smart Panels app
[CAM-14627] Deleting a tenant membership is not limited to the user or group
| Labels | New: SUPPORT |
| Component/s | New: engine [ 11656 ] |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Automation Platform 7.17.1 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When deleting a tenant membership using {{IdentityService#deleteTenantUserMembership}} or {{IdentityService#deleteTenantGroupMembership}} all memberships for the tenant are deleted. h3. Steps to reproduce (Required on creation): # Enable Authorization # Create two groups # Create a tenant # Create memberships for each tenant and group combination # Delete one membership using {{IdentityService#deleteTenantGroupMembership}} h3. Observed Behavior (Required on creation): All memberships related to the tenant are gone. h3. Expected behavior (Required on creation): Only the membership related to the respective group and tenant is deleted. h3. Root Cause (Required on prioritization): The {{WHERE}} condition in the SQL query doesn't restrict the deletion to the respective user or group. h3. Solution Ideas (Optional): Use queries that restrict the deletion to a user or group. h3. Hints (optional): * The same misbehavior exists for deleting tenant <-> user memberships. * See PR: |
New:
h3. Environment (Required on creation):
Camunda Automation Platform 7.17.1 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When deleting a tenant membership using {{IdentityService#deleteTenantUserMembership}} or {{IdentityService#deleteTenantGroupMembership}} all memberships for the tenant are deleted. h3. Steps to reproduce (Required on creation): # Enable Authorization # Create two groups # Create a tenant # Create memberships for each tenant and group combination # Delete one membership using {{IdentityService#deleteTenantGroupMembership}} h3. Observed Behavior (Required on creation): All memberships related to the tenant are gone. h3. Expected behavior (Required on creation): Only the membership related to the respective group and tenant is deleted. h3. Root Cause (Required on prioritization): The {{WHERE}} condition in the SQL query doesn't restrict the deletion to the respective user or group. h3. Solution Ideas (Optional): Use queries that restrict the deletion to a user or group. h3. Hints (optional): * The same misbehavior exists for deleting tenant <-> user memberships. * See PR: https://github.com/camunda/camunda-bpm-platform/pull/1902 |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Automation Platform 7.17.1 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When deleting a tenant membership using {{IdentityService#deleteTenantUserMembership}} or {{IdentityService#deleteTenantGroupMembership}} all memberships for the tenant are deleted. h3. Steps to reproduce (Required on creation): # Enable Authorization # Create two groups # Create a tenant # Create memberships for each tenant and group combination # Delete one membership using {{IdentityService#deleteTenantGroupMembership}} h3. Observed Behavior (Required on creation): All memberships related to the tenant are gone. h3. Expected behavior (Required on creation): Only the membership related to the respective group and tenant is deleted. h3. Root Cause (Required on prioritization): The {{WHERE}} condition in the SQL query doesn't restrict the deletion to the respective user or group. h3. Solution Ideas (Optional): Use queries that restrict the deletion to a user or group. h3. Hints (optional): * The same misbehavior exists for deleting tenant <-> user memberships. * See PR: https://github.com/camunda/camunda-bpm-platform/pull/1902 |
New:
h3. Environment (Required on creation):
Camunda Automation Platform 7.17.1 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When deleting a tenant membership using {{IdentityService#deleteTenantUserMembership}} or {{IdentityService#deleteTenantGroupMembership}} all memberships for the tenant are deleted. h3. Steps to reproduce (Required on creation): # Enable Authorization # Create two groups # Create a tenant # Create memberships for each tenant and group combination # Delete one membership using {{IdentityService#deleteTenantGroupMembership}} h3. Observed Behavior (Required on creation): All memberships related to the tenant are gone. h3. Expected behavior (Required on creation): Only the membership related to the respective group/user and tenant is deleted. h3. Root Cause (Required on prioritization): The {{WHERE}} condition in the SQL query doesn't restrict the deletion to the respective user or group. h3. Solution Ideas (Optional): Use queries that restrict the deletion to a user or group. h3. Hints (optional): * The same misbehavior exists for deleting tenant <-> user memberships. * See PR: https://github.com/camunda/camunda-bpm-platform/pull/1902 |
| Link | New: This issue is related to SUPPORT-13565 [ SUPPORT-13565 ] |
| Fix Version/s | New: 7.15.x [ 16600 ] | |
| Fix Version/s | New: 7.16.x [ 16897 ] | |
| Fix Version/s | New: 7.17.x [ 17395 ] | |
| Fix Version/s | New: 7.18.0 [ 17394 ] |
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 17418 ] |
| Assignee | New: Tassilo Weidner [ tassilo.weidner ] | |
| DRI | New: Tassilo Weidner [ tassilo.weidner ] |
| Assignee | Original: Tassilo Weidner [ tassilo.weidner ] | New: Nikola Koevski [ nikola.koevski ] |
| Resolution | New: Fixed [ 1 ] | |
| Reviewer | New: Nikola Koevski [ nikola.koevski ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Remaining Estimate | New: 0 minutes [ 0 ] | |
| Original Estimate | New: 0 minutes [ 0 ] |