Project

General

Profile

Actions

Bug #11312

open

New scopes are not added to a migrated pack

Added by Arshana Atapattu 4 months ago. Updated about 2 months ago.

Status:
QA
Priority:
Critical
Start date:
05/08/2024
Due date:
13/08/2024 (55 days late)
% Done:

100%

Estimated time:
Device Type:
Component:
Type:
Platform

Description

Environment details
Staging server(610)

Prerequisites
migrated pack(as of before 09.06.2024)

Steps
add a new scope and check if they are adding to the permissions(UI tree level)

Description
In a migrated setup, when a new scope was added they are not adding up in the permission set.
The permission is showing in the UI tree.
but when the permission was added in the UI, it throws an error.
EX: [1]

Reason: when a new tenant was created permission are getting from the super tenant permission.
but in this case a migrated pack's permission has not been updated with the latest permissions.
Therefore in both super and sub tenants are not showing the latest added scopes.

Related other ticket: https://roadmap.entgra.net/issues/11227

Result
Unable to update permissions in a migrated pack

[1]
TID: [-1234] [api/device-mgt/v1.0] [2024-06-10 05:09:31,215] ERROR {io.entgra.device.mgt.core.apimgt.webapp.publisher.APIPublisherServiceImpl} - Found invalid permission: /permission/admin/device-mgt/devices/any-group/permitted-actions-under-owning-group. Hence aborting the scope role mapping process

Actions #1

Updated by Rajitha Kumara 4 months ago

  • Due date set to 21/06/2024
Actions #2

Updated by Thilina Sandaruwan 3 months ago

  • Project changed from product-uem 6.2.0 GA to product-uem 5.3.0 GA
Actions #3

Updated by Arshana Atapattu 3 months ago

  • Project changed from product-uem 5.3.0 GA to product-uem 6.3.0 GA
Actions #4

Updated by Arshana Atapattu 2 months ago

  • Subtask #11466 added
Actions #5

Updated by Pahansith Gunathilake 2 months ago

  • Subtask deleted (#11466)
Actions #6

Updated by Pahansith Gunathilake 2 months ago

  • Due date set to 13/08/2024
  • Start date changed from 02/07/2024 to 05/08/2024
Actions #7

Updated by Pahansith Gunathilake 2 months ago

  • % Done changed from 100 to 0
Actions #8

Updated by Pahansith Gunathilake about 2 months ago

This can be eliminated by deleting the permission list using the carbon UI.
Steps to delete:
  1. Login to the carbon console as super admin.
  2. Go to the Resources section in Main tab.
  3. Click Browse and it'll open the registry browser.
  4. Navigate to the registry path /_system/governance/permission
  5. Delete the admin node by clicking actions -> delete
  6. Restart the product
Actions #9

Updated by Pahansith Gunathilake about 2 months ago

  • Status changed from New to QA
Actions #10

Updated by Pahansith Gunathilake about 2 months ago

  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF