Post-processing outstanding objects
Objects, which do not exist in the target system, can be marked as outstanding in One Identity Manager by synchronizing. This prevents objects being deleted because of an incorrect data situation or an incorrect synchronization configuration.
Outstanding objects
- Cannot be edited in One Identity Manager
- Are ignored by subsequent synchronization
- Are ignored by inheritance calculations
This means, all memberships and assignments remain intact until the outstanding objects have been processed. Start target system synchronization to do this.
To post-process outstanding objects
- In One Identity Manager, select the Cloud access management | Target system synchronization: Cloud Access Governance category.
All tables assigned to the target system type CIM as synchronization tables are displayed in the navigation view.
All objects that are marked as outstanding are shown. The Last log entry and Last method run columns display the time at which the last entry was made in the synchronization log and which processing method was run.
The No log available entry can mean the following
- The synchronization log has already been deleted.
- OR -
NOTE:
To display object properties of an outstanding object
- Select the object on the target system synchronization form.
- Open the context menu and click Show object.
- Select the objects you want to rework. Multi-select is possible.
-
Click one of the following icons in the form toolbar to run the respective method.
NOTE: Publish operation is not supported.
-
Table 11: Methods for handling outstanding objects
|
Icon |
Method |
Description |
|
|
Delete |
The object is immediately deleted in the One Identity Manager database. Deferred deletion is not taken into account. The Outstanding label is removed for the object. Indirect memberships cannot be deleted. |
|
|
Reset |
The Outstanding label is removed for the object. |
- Confirm the security prompt with Yes.
NOTE:
- By default, the selected objects are processed in parallel, which speeds up execution of the selected method. If an error occurs during processing, the action is stopped and all changes are discarded.
- Bulk processing of objects must be disabled if errors are to be localized, which means the objects are processed sequentially. Failed objects are named in the error message. All changes that were made up until the error occurred are saved.
To disable bulk processing
Speeding up synchronization with revision filtering
When you start synchronization, all synchronization objects are loaded. Some of these objects have not been modified since the last synchronization and, therefore, must not be processed. Synchronization is accelerated by only loading those object pairs that have changed since the last synchronization. One Identity Manager uses revision filtering to accelerate synchronization.
SCIM supports revision filtering. The Azure Cloud system object's date of last change is used as revision counter. Each synchronization saves its last execution date as a revision in the One Identity Manager database (table DPRRevisionStore, column Value). This value is used as a comparison for revision filtering when the same workflow is synchronized the next time. When this workflow is synchronized the next time, the Azure cloud system object's change date is compared with the One Identity Manager revision saved in the database. Only those objects that have been changed since this date are loaded from the Azure Cloud System.
The revision is found at start of synchronization. Objects changed after this point are included with the next synchronization.
Revision filtering can be applied to workflows and start up configuration.
To permit revision filtering on a workflow
-
Open the synchronization project in the Synchronization Editor.
-
Edit the workflow properties. Select the entry Use revision filter from Revision filtering.
To permit revision filtering for a start up configuration
-
Open the synchronization project in the Synchronization Editor.
-
Edit the start up configuration properties. Select the entry Use revision filter from Revision filtering.
For more detailed information about revision filtering, see the One Identity Manager Target System Synchronization Reference Guide.
Help for the analysis of synchronization issues
You can generate a report for analysing problems which occur during synchronization, for example, insufficient performance. The report contains information such as:
-
Consistency check results
-
Revision filter settings
-
Scope applied
-
Analysis of the synchronization buffer
-
Object access times in the One Identity Manager database and in the target system
To generate a synchronization analysis report
-
Open the synchronization project in the Synchronization Editor.
-
Select the menu Help | Generate synchronization analysis report and answer the security prompt with Yes.
The report may take a few minutes to generate. It is displayed in a separate window.
-
Print the report or save it in one of the available output formats.
Deactivating synchronization
Regular synchronization cannot be started until the synchronization project and the schedule are active.
To prevent regular synchronization
-
Open the synchronization project in the Synchronization Editor.
-
Select the start-up configuration and deactivate the configured schedule.
Now you can only start synchronization manually.
An activated synchronization project can only be edited to a limited extend. The schema in the synchronization project must be updated if schema modifications are required. The synchronization project is deactivated in this case and can be edited again.
Furthermore, the synchronization project must be deactivated if synchronization should not be started by any means (not even manually).
To deactivate the synchronization project
-
Open the synchronization project in the Synchronization Editor.
-
Select General on the start page.
-
Click Deactivate project.
Related Topics
Basic Data for managing Azure Cloud System
To manage an Azure cloud system environment in One Identity Manager, the following basic data is relevant.
Target system managers
A default application role exists for the target system manager in One Identity Manager. Assign the employees who are authorized to read all Azure related objects and the Active directory User, Group and Service Principal objects for the Azure Active Directory tenants in One Identity Manager to this application role. Define additional application roles if you want to limit the edit or view permissions for target system managers to individual tenants. The application roles must be added under the default application role.
For more information about implementing and editing application roles, see the One Identity Manager Authorization and Authentication Guide.
Implementing application roles for target system managers
- The One Identity Manager administrator assigns employees to be target system managers.
- These target system managers add employees to the default application role for target system managers. Target system managers with the default application role are authorized to edit all tenants in One Identity Manager.
- Target system managers can authorize other employees within their area of responsibility as target system managers and if necessary, create additional child application roles and assign these to individual connections.
Default Application Roles for Target System Managers
Table 12: Default Application Roles for Target System Managers
|
Users |
Tasks |
|
Target system managers |
Target system managers must be assigned to Target systems | Cloud Access Governance or a sub-application role. Users with this application role:
Assume administrative tasks for the target system.
-
Read objects like user accounts, groups, service principals, Management groups, subscriptions, resource groups, resource, roles and role assignments.
-
Configure synchronization in the Synchronization Editor and defines the mapping for comparing target systems and One Identity Manager.
-
Edit the synchronization's target system types and outstanding objects.
-
Authorize other employees within their area of responsibility as target system managers and create child application roles if required. |
To initially specify employees to be target system administrators
-
Log in to One Identity Manager as Manager administrator (Base role | Administrators).
-
Select One Identity Manager Administration | Target systems | Administrators.
-
Select Assign employees.
To add the first employees to the default application as target system managers
-
Log into One Identity Manager as Target System Administrator (Target systems | Administrators).
-
Select One Identity Manager Administration | Target systems | Cloud Access Governance.
-
Select Assign employees in the Task view.
-
Assign the employees you want and save the changes.
To authorize other employees as target system managers when you are a target system manager
-
Log into One Identity Manager as target system manager.
-
Select the application role in Cloud Access Management | Basic configuration data | Target system managers.
-
Select Assign employees.
-
Assign the employees you want and save the changes.
To specify target system managers for individual clients
-
Log into One Identity Manager as target system manager.
-
Select Cloud Access Management | Tenants.
-
Select the client from the result list.
-
Select Change master data.
-
On the General tab, select the application role in the Azure Cloud System manager field.
NOTE: In case the Azure Cloud Target System Manager field is not present, install the AAD.Forms.vif refer to KB article (CIM Enhancement for AAD Module).
-
Next to the Target system manager menu, click to create a new application role.
-
Enter the application role name and assign the Target systems | Cloud Access Governance parent application role.
-
Click OK to add the new application role.
-
Save the changes.
-
Assign employees to this application role who are permitted to edit the client in One Identity Manager.
Azure Active Directory Tenant
You must provide details about your organization the first time you register for a Microsoft cloud service. This detailed information is used to make a new Azure Active Directory partition. The organization represents one Azure Active Directory tenant. In One Identity Manager, you can edit the main data of each Azure Active Directory tenant.
However, you cannot create new Azure Active Directory tenants in One Identity Manager.
General Master Data for Microsoft Azure Connection
To edit CIM Target system manager for Azure Active Directory tenant data
-
In the Manager, select the Azure Active Directory > Tenants category.
-
In the result list, select the Azure Active Directory tenant.
-
Select the Change main data task.
-
Edit the Azure Cloud Target System Manager field for Azure Active Directory tenant.
-
Save the changes.
Detailed information about this topic
More details can be found in Azure Active Directory Synchronization Admin Guide
Managing Azure Cloud System Objects
The following are the Azure objects that are synchronized from the target azure tenant.
Azure Scope Objects
Root Scope(/)
RootScope is the top most level scope above the management group. If the user's access is elevated, the user is assigned the User Access Administrator role in Azure at root scope (/). All role assignments defined at the rootscope will be inherited at all levels below. Role assignments at the rootscope can be defined using Azure PowerShell, Azure CLI, or the REST API.
Management Group
Management Groups provide a scope above Subscriptions. All Subscriptions within a Management Group inherit conditions applied at the management group. Governance policies can be applied to Management Group so that Subscriptions inherit it. By default, all Azure Tenants automatically have a Root Management Group created.
Each directory is given a single top-level management group called the root management group. The root management group is built into the hierarchy to have all management groups and subscriptions fold up to it.
Azure management groups support Azure role-based access control for all resource accesses and role definitions. These permissions are inherited to child resources that exist in the hierarchy.
Subscription
Azure Subscriptions are the container that hosts all Azure Resources. It is the Resource access and billing boundary
Resource Groups
Azure Resource Group is a container that holds the related resources needed for a particular solution. Resource Groups are created under an Azure Subscription.
The resource group stores metadata about the resources. Therefore, when you specify a location for the resource group, you are specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region.
Resources
Azure Resource is the entity such as virtual machine that is managed by Azure.
These are the building blocks of an Azure IT environment. The resources are organized into Resource Groups inside of an Azure subscription. There are billable and non-billable resources. Billable resources have a Meter attached to them that runs while the resource is provisioned.
Roles
Azure Roles is a collection of permissions and defines the following:
-
List of Actions that can be performed the Resource
-
List of Actions that are excluded from the allowed list of Actions
-
List of Actions that can be performed on the underlying data
-
List of Actions that are excluded from the allowed list of data actions
Role definitions are created at a particular scope (Management Group / Subscriptions / Resource Group) and can be assigned to AAD Users / AAD Service Principal / AAD Managed Identities at the scope at which Role was created or at a child scope level. Example: The Built in Owner role was created at the Root Management Scope level. This role can be assigned to an AADUser at the Management scope level or at a child scope level such as Subscription or Resource.
Built in Roles
Built in Roles are created by Azure at Root Management Group Scope and cannot be modified.
Custom Roles
Custom Roles can be created and assigned multiple scopes at Management Group / Subscriptions / Resource Group level.
Locations / Regions
Azure Regions contain the Azure Data Centers. When a Resource Group / Resource is created we select the Azure Region where the resource is created, and its data resides
Resource Types
Azure Resource Provider is a service that supplies resources. Example Microsoft.Compute. Resource Types are resources available through the Resource Provider. Example VMs. Each Resource Type is available for deployment on certain regions. The API lists the regions on which a particular Resource Type is available for deployment.
Role Assignments
Built in Roles and Custom Roles can be assigned to AAD User, AAD Service Principal, AAD Group and Managed Identities at various scopes. The roles are also inherited based on scope hierarchy.
