Click HERE to see how Saviynt Intelligence is transforming the industry. |
08/05/2024 11:49 AM
We use IBM to import our users into Saviynt. Those users are supposed to receive a manager. In IBM we use the employeenumber, not username, to identify the users manager. In our connection to import the users, there is no where in the USER_ATTRIBUTE section that has the manger or a way to link the employeenumber to the username for the manager. In the INCREMENTAL_CONFIG manager is listed.
How can I get Saviynt to link the employeenumber from IBM for the users manager to the username of the manager in Saviynt?
The only other thing I could think of was there may be something configurable in Global Settings to make this happen. I am at a loss to be honest. Mind you I did not build this. I am trying to fix something and have no background really on what is going on.
One last question. Do all the fields in the INCREMENTAL_CONFIG have to mapped in the USER_ATTRIBUTES for it import. My logic says yes and if I am correct I was hoping for confirmation.
[CITY::l#String,
Country::c#String,
CREATEDBY::creatorsname#String,
DEPARTMENTNUMBER::departmentnumber#String,
DEPARTMENTNAME::departmentname#String,
DISPLAYNAME::displayname#String,
EMAIL::mail#String,
EMPLOYEETYPE::hrpersontype#String,
EMPLOYEEID::employeenumber#String,
FIRSTNAME::givenname#String,
JOBCODE::ihcjobglnumber#String,
JOBDESCRIPTION::title#String,
LASTNAME::sn#String,
LOCATION::ihcfacilityabbr#String,
LOCATIONDESC::location#String,
LOCATIONNUMBER::destinationIndicator#String,
MIDDLENAME::middlename#String,
SYSTEMUSERNAME::unitnumber#String,
PHONENUMBER::telephonenumber#String,
PREFEREDFIRSTNAME::knownas#String,
REGION::departmentfacility#String,
REGIONCODE::deptfacilitynum#String,
SECONDARYPHONE::mobile#String,
STATE::st#String,STREET::street#String,
TERMDATE::termdate#customDate--dd-MMM-yy,
USERNAME::uid#String,
statuskey::isaccountenabled#number,
CREATEDATE::createtimestamp#customDate--yyyyMMddHHmmss,
UPDATEDATE::modifytimestamp#customDate--yyyyMMddHHmmss,
CUSTOMPROPERTY3::providerstatus#string,
LASTSYNCDATE::hrupdate#customDate--dd-MMM-yy,
CUSTOMPROPERTY4::studentstatus#String,
CUSTOMPROPERTY5::volunteerstatus#String,
CUSTOMPROPERTY13::ihcbusinessunit#String,
CUSTOMPROPERTY7::volunteer_id#String,
CUSTOMPROPERTY12::ihcadplacementattr#String,
CUSTOMPROPERTY14::provider_id#String,
CUSTOMPROPERTY10::ihccernplacementattr#String,
CUSTOMPROPERTY11::ihcemployee#String,
CUSTOMPROPERTY15::ihcempid#String,
CUSTOMPROPERTY16::national_prov_id#String,
CUSTOMPROPERTY17::userNCID#String,
CUSTOMPROPERTY19::providerrole#String,
CUSTOMPROPERTY28::ihcmgmtcomt#String,
CUSTOMPROPERTY59::ihcpwdadexpiration#String,
CUSTOMPROPERTY20::loginstatus#String,CUSTOMPROPERTY23::ihcbadgenum#String,
CUSTOMPROPERTY24::termacceptance#String,
CUSTOMPROPERTY61::employeetype#String,
CUSTOMPROPERTY62::ihcexemptstatus#String,
CUSTOMPROPERTY63::ihcprovideraffiliation#String,
CUSTOMPROPERTY56::externalid#String,
CUSTOMPROPERTY58::ihcrefreshattr#String,
STARTDATE::ihchiredate#customDate--dd-MMM-yyyy]
{
"incrementalImportType": "changeNumber",
"changeLogBase": "cn=changelog",
"changeNumberFilter": "&(changeNumber>=##MAX_CHANGENUMBER##)(targetDN=*,ou=mspr,ou=ihcpeople,o=ihc)",
"dnAttributeName": "targetDn",
"dnAttributeNameMappedTo":"username",
"changeNumberAttrName": "changeNumber",
"changeTypeAttrName": "changeType",
"changedFeildsInScope": "l,c,creatorsname,departmentnumber,ihcmgmtcomt,departmentname,displayname,mail,hrpersontype,ihcjobfamily,employeenumber,givenname,ihcjobglnumber,title,sn,ihcbusinessunit,ihcfacilityabbr,location,middlename,uid,telephonenumber,knownas,departmentfacility,deptfacilitynum,mobile,st,street,unitnumber,ihcjobglnunmber,manager,isaccountenabled,ihcrefreshattr,createtimestamp,modifytimestamp,providerstatus,hrupdate,studentstatus,volunteerstatus,ihcadplacementattr,ihcpwdadexpiration,ihcemployee,Dn,ihccernplacementattr,provider_id,ihccernplacementattr,ihcemployee,ihcempid,national_prov_id,userNCID,providerrole,loginstatus,dummy,ihcbadgenum,termacceptance,ihcexemptstatus,employeetype,externalid,destinationIndicator",
"changesLogAttrName": "changes",
"searchAttribute": "entrydn",
"searchOn" : "rdn",
"objectFilterForUsers" :" "
}
Thank you so much for your help.
08/07/2024 12:51 AM
Please use the corresponding connector's official guide to refer the mappings.
Regards,
Dhruv Sharma
08/07/2024 01:14 AM
Hi @ScotRawlings , which connector are you using AD?
08/14/2024 06:32 PM
Well it looks like we have given it a strong effort but I am happy to say we are skipping the shortcut and creating a new connector for our identity source, cleaning things up, and using username for manager. I am very happy to say the least.