Access Profiles Migration Using Configuration Hub

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi All,

We are migrating Configuration from a tenant to another using configuration Hub, while migrating the acces profiles we noticed that it is not replacing the entitlement ID and still adding the entitlement with the old ID.

"entitlements": [
    {
      "id": "2837fff93xn38x3291n991bx91b9b19",
      "type": "ENTITLEMENT",
      "name": "x Dept"
    }
],

when we removed " " it worked fine and replaced IDs correctly.

"entitlements": 
    {
      "id": "8e42b2de954d4531844561df000dfccc",
      "type": "ENTITLEMENT",
      "name": "Aggregation Dept_"
    },

is there any way to automate that rather than doing that for each entitlement in each access profile ?

Best Regards,
Ahmed Nasr

2

Hi, configuration hub should try and resolve the references to entitlements in the target tenant whenever the referenced json object contains the name of the object as well. When migrating from another tenant, it should first try to lookup for entitlement by name and replace the id.
Same should happen for any other referenced object. We did notice that some of the configurations only referencing by id and in that case, when the type and name does not exist, it fails to resolve the referenced object. We are working to identify these cases and make sure they are all automatically resolving referenced when migrating configs between tenants

3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.