Advice regarding LDAP import coalesce (ObjectGUID)

[Niels Aksel]

Hi Community!

I'm looking for advice regarding LDAP import of users from AD

We would like to coalesce on ObjectGUID, but I'm unsure what is the best approach

• When reading the ObjectGUID from Active Directory, the value is converted to an encode64 string, looking something like "O5IgH564Jxxxx==", which I guess is okay?
• Do I simply create a new string attribute on sys_user table (u_guid) to store this value and change to coalesce on the custom attribute when all records are updated?
• Since this will be the only attribute we coalesce on, do I need to create a new index or I do simply disregard the warning I get in the transform map (Coalesce field not indexed)? We are importing around 20.000 user records

[Patrick DeCarl1 · Accepted solution]

Niels,

I have done the same thing for many clients. ObjectGUID is a good key to use. However, if you already have users in the system you might need to use a different field to coalesce to get the ObjectGUID in first and then switch to objectguid to coalesce.   A new string value will work and just make sure you create the char size big enough on user table and the import table.   It doesn't hurt to create the new index.  

[Niels Aksel]

Thanks Patrick,

I got the ObjectGUID in and change our coalesce settings afterwards. Working fine with no issues

[James Roehling1]

What were you using as the Source Field? Sys ID?
I"ve created the ObjectGUID column in the sys_user table. I'm just not exactly sure which Source Field to use. I also set a char limit of 100. (Figured this should be good enough.)