Actions
Bug #12658
closedBacklog - Bug #12552: ADMX ingestion related bugs and improvements
Cannot create same ADMX files for two tenants
Start date:
24/02/2025
Due date:
% Done:
100%
Estimated time:
Device Type:
Windows
Component:
Device Management
Type:
Description
Environment details
Staging Server: 6.4.0
- Add an ingestion ADMX file for a specific tenant.
- Switch to another tenant.
- Go to the ingestion policy configuration.
- Add the same ADMX file for the current tenant as well.
Description
In the current implementation, we use maps to store tenant, file name, and feature code data. Due to this approach, the same ADMX file cannot be created for multiple tenants.
Proposed Fix
To resolve this issue, we need to manage ADMX files and feature codes separately for each tenant. This can be achieved by modifying the feature code prefix to include a unique tenant-specific identifier and adding composite key using the tenant ID and the generated unique feature code.
Files
Updated by Thilina Sandaruwan about 1 month ago
- Subject changed from Cannot create same ADMX files for 2 tenants to Cannot create same ADMX files for two tenants
- Priority changed from High to Critical
Updated by Thilina Sandaruwan about 1 month ago
- Status changed from New to QA
- % Done changed from 0 to 100
Updated by Thilina Sandaruwan about 1 month ago
- File Screenshot from 2025-02-25 07-49-32.png added
Updated by Thilina Sandaruwan about 1 month ago
- Status changed from QA to Implementation
- % Done changed from 100 to 0
Updated by Thilina Sandaruwan about 1 month ago
- File Screenshot from 2025-02-25 07-49-32.png Screenshot from 2025-02-25 07-49-32.png added
- Status changed from Implementation to QA
- % Done changed from 0 to 100
Updated by Thilina Sandaruwan about 1 month ago
Updated by Thilina Sandaruwan about 1 month ago
Change migration script with Pr: https://github.com/entgra-proprietary/product-uem/pull/18
Updated by Thilina Sandaruwan about 1 month ago
- File deleted (
Screenshot from 2025-02-25 07-49-32.png)
Updated by Arshana Atapattu about 1 month ago
- Status changed from QA Accept to Closed
Closing due to QA accept
Actions