Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On This Page

...

User Job Mapping jobs do not transfer any data. They are used to map user accounts on the source and destination platforms. The User Job Mapping job automatically generates child jobs based on the settings you’ve chosen for the job. These child jobs perform all the data transfers. You can select an account map to use for automatic user mapping rules and exceptions and filter out users by explicitly including or excluding them.

...

Info

If you want to create a User Job Mapping job that integrates with LDAP, you must use a REST API call to create the job and add the mapping. See Account and Group Maps Using LDAP for more information. 

Adding Locations

In addition to choosing the source and destination platforms that will be used for the User Job Mapping job, you need to specify the child job source and destination paths that should be used when creating the child jobs. This directory within each folder will be used as the source.

...

  • Map specific users to one another: Select this option to use an existing account/user map you already created to map users. Select the map you want to use for this job from the list. 

  • Create new user map policy: Select this option to create a new user map. Refer to Permission | Account Map/Group Map for more information about the options used to create the user map. 

  • User Account Job Generation: Use this section to identify which connection should be used to determine user accounts. If you select Source, DryvIQ will use the source connection as the source of user accounts when generating user account jobs. If you select Destination, DryvIQ will use the destination connection as the source of user accounts when generating user account jobs.

  • Remove user account jobs that are no longer valid: This is an on/off setting that deletes jobs that are no longer valid.

  • Email Domain: Specify an email domain to limit the generation of User job mapping child jobs to only users with this email domain. For example, enter "example.com" to create a job for the user "test@example.com" but not for the user "test@something.com."

  • Import user filters: Import an inclusion or exclusion mapping file that should be applied to the job. You can upload the file from your computer or use a file on the source platform. (See Account Map/Group Map CSV Guidelines for information about generating mapping files used to include or exclude users.)
    An inclusion map specifies users to include when generating child jobs. Child jobs are only created for users in the map that can be matched. All other users will be excluded. 
    An exclusion map specifies users to exclude when generating child jobs. Child jobs will not be created for the users in this map. Jobs will be created for all other users. 

...