ommodu change GLOBAL_UNIQUE_ID with no reason

[echen]

When I run the following command, it mysteriously changed GLOBAL_UNIQUE_ID.

>/opt/scalix/bin/ommodu -F add -n "CN=Eric Chen/G=Eric/S=Chen/OU1=mtc/INTERNET-ADDR=chen@mydomain.com=chen@mydomain2.com=echen@mydomain3.com" -c +admin,+mboxadmin --authid chen --class full -o "CN=Eric Chen/G=Eric/S=Chen/OU1=abc"


I got this problem when I tried to use omldapsync to synchronize Fedaror LDAP Server to Scalix.

I used to map entryid to GLOBAL_UNIQUE_ID. Recently, I changed to map uid to GLOBAL_UNIQUE_ID. Since then, if I run sync, GLOBAL_UNIQUE_ID was mysteriously changed to old one-entryid.

I traced down to scalix-res.log, I found that the sync process actually run two command,
>/opt/scalix/bin/ommodent -n ADMINISTERED-BY=ldapsync-AD_SX1/GLOBAL-UNIQUE-ID=chen/E
X-CDA-DIRECTORY=/FOREIGN-ADDR=uid\=chen,ou\=People,dc\=mydomain,dc\=com -e CN=Eric Chen/G=Eric/S=Chen/OU1=mtc

and the one I list at begin.

The first command is fine. The GLOBAL_UNIQUE_ID was changed to "chen", but after the second command, the GLOBAL_UNIQUE_ID was change back to old value "10".

I have no idea how that happen.

any help is appreciate.

[dannyt]

Hi,

Since omldapsync relies on the GUID to perform its updates, if the GUID changes (as it is the case for you because you have remapped it to somehting else) then it will run into problem because the GUID exists in both the USERLIST and SYSTEM directory and ommodent only changes the SYSTEM while ommodu will read the original from USERLIST and update SYSTEM to it.

For a brand new user it should work OK as expected. Whenever the GUID mapping is changed, the synced data ought to be cleared out on the Scalix side and start from scratch.

Regards,
Danny

[echen]

You are absolutely right. For the new user, the sync works perfectly. Is there a way I can change USERLIST and SYSTEM rather than delete all the old user and create it again.

[dannyt]

I would still recommend a clean up and resync if GUID mapping has been changed. If you really must know, you can try the followings (warning: can cause damage):

ommodent -t h -d userlist -e cn="<common name>" -n GLOBAL-UNIQUE-ID="<new guid>"
ommodent -e cn="<common name>" -n GLOBAL-UNIQUE-ID="<new guid>"

Note the data files maintained by omldapsync internally may be in a state that will need to be reset in some way - see man page of omldapsync for details.

Danny