mapping.properties

Overview

Before migrating Identity Brokerage connectors in IGI as services into IVIG, it is required to upload the corresponding service profile to IVIG (whose details can be obtained from Service types report). It is recommended to use the same profile that was used in IGI to upload to IVIG. If there are any changes in the profiles being uploaded to both the products, these differences must be specified in the mapping.properties file.

Same service profile in IGI and IVIG

When the profiles being uploaded are same in IGI and IVIG, below properties are used. It is advised to not to change these properties. These properties define how the data should be mapped from IGI to IVIG when creating services. Once the read operation for IB connectors is carried out, a CSV file containing the driver configuration details is generated. By default, values from the columns of this CSV file are matched to the related IVIG attributes of the service in IVIG.

ivig.service.create-service.profile.attrColumnName=DRIVER_PROPERTY_NAME

ivig.service.create-service.profile.attrValueColumnName=DRIVER_PROPERTY_VALUE

ivig.service.create-service.profile.serviceColumnName=CONNECTOR_NAME

ivig.service.create-service.profile.profileColumnName=PROFILE_REF

Different service profile in IGI and IVIG

When different service profiles are used in case of IGI and IVIG, use properties in below format in the mapping.properties file to define the mapping between the attributes. In case the attributes in both the profiles have same name, additional properties need not be added.

For example, consider "Active Directory Profile" is used in IGI and "ADProfile" is used in IVIG. Suppose both these profiles have common attributes like eruid, cn, sn, etc., these attributes need not be defined in the mapping.properties file.

In case the attributes in both these profiles are different, for e.g., "eruid" in "Active Directory Profile" corresponds to "EmployeeID" in "ADProfile", specify these details in below format.

When setting up custom attribute mappings, you must specify the number of profiles for which the mappings will be defined. Each profile can have its own mapping configuration, allowing for more flexible and targeted service creation.

#ivig.service.create-service.profile.count=<profileCount>
ivig.service.create-service.profile.count=1

#igi.service.create-service.profile1.name=<IGI_profile_name_1>
igi.service.create-service.profile1.name=Active Directory Profile

#ivig.service.create-service.profile1.name=<IVIG_profile_name_1>
ivig.service.create-service.profile1.name=ADProfile

#ivig.service.create-service.profile<n>.attributes.<ivig_attribute_name>=<igi_attribute_name_from_CSV>
#ivig.service.create-service.profile1.attributes.EmployeeID=eruid