Each mapping rule applies to a scope of objects. By default, this scope includes all objects that belong to the object types specified in the mapping rule. If necessary, you can narrow the scope specified for a particular mapping rule or you can revert to the default scope.
To change the scope of a mapping rule
-
In the Console, open Mapping.
-
Click the name of the appropriate connection.
-
Click the appropriate mapping pair entry.
-
Locate the mapping rule whose scope you want to change. Use the following elements provided for each mapping rule entry:
-
Mapping scope for system 1: Shows the mapping rule scope applicable to the data system shown on the left part of the mapping pair entry.
-
Mapping scope for system 2: Shows the mapping rule scope applicable to the data system shown on the right part of the mapping pair entry.
These elements can take one of the following values:
-
Default: Indicates that the mapping rule applies to all objects of the specified type.
-
Custom: Indicates that the mapping rule scope is narrowed down and only applies to some objects of the specified type.
-
Change the mapping rule scope as necessary:
-
Click the value displayed next to Mapping scope for system 1 or Mapping scope for system 2, and then specify the scope you want to use.
-
When you are finished, click OK.
Once you have created mapping rules for a mapping pair, you have to run the map operation in order to apply these rules and map objects that belong to the mapping pair.
There are two methods to run the map operation:
-
Running the map operation once, manually.
-
Creating a recurring schedule to automatically run the map operation on a regular basis.
TIP: This method is recommended when you want to use to synchronize passwords from an Active Directory domain to other connected systems.
Running the map operation once, manually
This method allows you to run your mapping rules without creating a recurring schedule.
To run the map operation once, manually
-
In the Console, open Mapping.
-
Click the name of the connection for which you want to run the map operation.
-
Click the mapping pair for which you want to run the map operation.
-
Click Map now.
-
In the dialog that opens, click one of the following:
-
Full Map: With this option, retrieves the data required to map objects from the connected data systems.
-
Quick Map: With this option, first tries to map objects by using the data that is available in the local cache. If the local cache is missing or cannot be used to map objects, then retrieves the required data from the connected data systems.
Wait for the map operation to complete.
After the map operation is completed, the displays a report that provides information about the objects that participated in the map operation. At this stage, the application does not map the objects. To map the objects, you have to commit the map operation result.
You can click the number that is provided next to an object category name in the report to view the details of objects that belong to that category.
-
Review the report about the objects that participated in the map operation, then click Commit to map the objects.
Creating a recurring schedule to automatically run the map operation on a regular basis
Running mapping rules on a recurring schedule allows you to properly map newly-created Active Directory user objects to their counterparts in the connected systems where you automatically synchronize passwords with the Active Directory domain. If you do not run mapping rules on a regular basis, some passwords may become out of sync due to the changes that inevitably occur to your environment. For example, new user objects are created, some user objects are deleted, but cannot detect these changes and synchronize passwords for the newly-created users before you apply the mapping rules. In this scenario, the best way to ensure synchronizes all passwords is creating a recurring schedule for applying your mapping rules on a regular basis.
To create a recurring schedule to automatically run the map operation on a regular basis
-
In the Console, open Mapping.
-
Click the name of the connection for which you want to create a recurring mapping schedule.
-
Click the mapping pair for which you want to run the map operation on a recurring schedule.
-
Click Schedule mapping.
-
In the dialog that opens, select the Schedule the task to run check box, and then specify a schedule for the map operation.
One Identity recommends that you schedule the map operation to run once in every 6 hours.
-
If several instances are installed in your environment, under Run the task on, select the computer that hosts the instance you want to use for running the map operation.
-
Click OK to activate the schedule.
The results of a scheduled map operation always apply automatically. As a result, you do not have to commit the changes after the scheduled operation is completed.
When performing a scheduled map operation, always retrieves the required data from the connected data systems and never uses the data available in the local cache.
You can unmap the objects that were mapped earlier.
To unmap objects
-
In the Console, open Mapping.
-
Click the name of the connection for which you want to unmap objects.
-
Click the mapping pair that specifies the objects types you want to unmap.
-
Click Unmap now and wait until the unmap operation completes.
After the unmap operation is completed, the displays a report that provides information about the objects that participated in the unmap operation. At this stage, the application does not unmap the objects. To unmap them, you need to commit the result of the unmap operation.
To view the details of objects that belong to a given object category, you can click the number provided next to the object category name in the report.
-
Review the report on the objects that participated in the unmap operation, and then click Commit to unmap the objects.
Automated password synchronization
If your enterprise environment has multiple data management systems, each having its own password policy and dedicated user authentication mechanism, you may face one or more of the following issues:
-
Because users have to remember multiple passwords, they may have difficulty managing them. Some users may even write down their passwords. As a result, passwords can be easily compromised.
-
Each time users forget one or several of their numerous access passwords, they have to ask administrators for password resets. This increases operational costs and translates into a loss of productivity.
-
There is no way to implement a single password policy for all of the data management systems. This too impacts productivity, as users have to log on to each data management system separately in order to change their passwords.
With , you can eliminate these issues and significantly simplify password management in an enterprise environment that includes multiple data management systems.
provides a cost-effective and efficient way to synchronize user passwords from an Active Directory domain to other data systems used in your organization. As a result, users can access other data management systems using their Active Directory domain password. Whenever a user password is changed in the source Active Directory domain, this change is immediately and automatically propagated to other data systems, so each user password remains in sync in the data systems at all times.
You need to connect to the data systems in which you want to synchronize passwords through special connectors supplied with .
