OMLDAPSYNC ignoring search filter in sync.cfg?
Posted: Tue Mar 28, 2006 2:54 pm
Hi,
I have omldapsync working but not exactly getting the behavior I would
have expected given the LDAP search filter I provided. In order to
prevent omldapsync from importing non-Scalix system accounts, I set the
filter to only include LDAP entries that contain the attribute
exScalixObject=TRUE as shown in the filter line in my sync.cfg file
excerpt just below:
EX_FILTER=(|(&(objectclass=inetOrgPerson)(mail=*)(exScalixObject=TRUE))(&(objectclass=groupOfNames)(mail=*)))
I added the new filter item into the first "anded" section of the search
filter.
When I subsequently run the omldapsync command in test mode, it still
indicates that it will bring in all 39 OpenLDAP accounts when only 2 of
them actually contain the exScalixObject attribute.
Please let me know what I am doing wrong with the filter or why omldapsync
is apparently ignoring it.
Thanks,
Pat
=============== OUTPUT FROM omldapsync===============
[root@mxlx01p dslx01p]# omldapsync -n -u dslx01p
2006-03-28 10:45:22 STATUS: test LDAP dir sync import dslx01p started
###############
2006-03-28 10:45:23 INFO: work dir is /var/opt/scalix/ldapsync/dslx01p/import
2006-03-28 10:45:23 STATUS: reprocess search results from
dslx01p.be.sddc1.luthresearch.com ...
2006-03-28 10:45:23 STATUS: find delta and perform mapping ...
2006-03-28 10:45:23 INFO: ... 0 entries to delete
2006-03-28 10:45:23 INFO: ... 39 entries to add
2006-03-28 10:45:23 INFO: ... 0 entries to modify
2006-03-28 10:45:23 STATUS: test apply membdelete data against Scalix ...
2006-03-28 10:45:23 INFO: ... 0 entries passed for member.curr
2006-03-28 10:45:23 INFO: ... 0 entries failed for member.curr
2006-03-28 10:45:23 INFO: ... 0 entries warned for member.curr
2006-03-28 10:45:23 STATUS: test apply delete data against Scalix ...
2006-03-28 10:45:23 INFO: ... 0 entries passed for delete.curr
2006-03-28 10:45:23 INFO: ... 0 entries failed for delete.curr
2006-03-28 10:45:23 INFO: ... 0 entries warned for delete.curr
2006-03-28 10:45:23 STATUS: test apply add data against Scalix ...
2006-03-28 10:45:40 INFO: ... 39 entries passed for add.curr
2006-03-28 10:45:40 INFO: ... 0 entries failed for add.curr
2006-03-28 10:45:40 INFO: ... 0 entries warned for add.curr
2006-03-28 10:45:40 STATUS: test apply limit data against Scalix ...
2006-03-28 10:45:41 INFO: ... 0 entries passed for add.curr
2006-03-28 10:45:41 INFO: ... 0 entries failed for add.curr
2006-03-28 10:45:41 INFO: ... 0 entries warned for add.curr
2006-03-28 10:45:41 STATUS: test apply modify data against Scalix ...
2006-03-28 10:45:41 INFO: ... 0 entries passed for modify.curr
2006-03-28 10:45:41 INFO: ... 0 entries failed for modify.curr
2006-03-28 10:45:41 INFO: ... 0 entries warned for modify.curr
2006-03-28 10:45:41 STATUS: test apply limit data against Scalix ...
2006-03-28 10:45:41 INFO: ... 0 entries passed for modify.curr
2006-03-28 10:45:41 INFO: ... 0 entries failed for modify.curr
2006-03-28 10:45:41 INFO: ... 0 entries warned for modify.curr
2006-03-28 10:45:41 STATUS: test apply membadd data against Scalix ...
2006-03-28 10:45:42 INFO: ... 0 entries passed for member.curr
2006-03-28 10:45:42 INFO: ... 0 entries failed for member.curr
2006-03-28 10:45:42 INFO: ... 0 entries warned for member.curr
2006-03-28 10:45:42 STATUS: test apply membmodify data against Scalix ...
2006-03-28 10:45:42 INFO: ... 0 entries passed for member.curr
2006-03-28 10:45:42 INFO: ... 0 entries failed for member.curr
2006-03-28 10:45:42 INFO: ... 0 entries warned for member.curr
2006-03-28 10:45:42 INFO: test mode - keep current search result for
reprocessing
2006-03-28 10:45:42 STATUS: test LDAP dir sync import dslx01p completed
#############
2006-03-28 10:45:42 STATUS: test LDAP dir sync export dslx01p started
###############
2006-03-28 10:45:42 INFO: agreement type 13 only supports import operation
2006-03-28 10:45:42 STATUS: test LDAP dir sync export dslx01p completed
#############
I have omldapsync working but not exactly getting the behavior I would
have expected given the LDAP search filter I provided. In order to
prevent omldapsync from importing non-Scalix system accounts, I set the
filter to only include LDAP entries that contain the attribute
exScalixObject=TRUE as shown in the filter line in my sync.cfg file
excerpt just below:
EX_FILTER=(|(&(objectclass=inetOrgPerson)(mail=*)(exScalixObject=TRUE))(&(objectclass=groupOfNames)(mail=*)))
I added the new filter item into the first "anded" section of the search
filter.
When I subsequently run the omldapsync command in test mode, it still
indicates that it will bring in all 39 OpenLDAP accounts when only 2 of
them actually contain the exScalixObject attribute.
Please let me know what I am doing wrong with the filter or why omldapsync
is apparently ignoring it.
Thanks,
Pat
=============== OUTPUT FROM omldapsync===============
[root@mxlx01p dslx01p]# omldapsync -n -u dslx01p
2006-03-28 10:45:22 STATUS: test LDAP dir sync import dslx01p started
###############
2006-03-28 10:45:23 INFO: work dir is /var/opt/scalix/ldapsync/dslx01p/import
2006-03-28 10:45:23 STATUS: reprocess search results from
dslx01p.be.sddc1.luthresearch.com ...
2006-03-28 10:45:23 STATUS: find delta and perform mapping ...
2006-03-28 10:45:23 INFO: ... 0 entries to delete
2006-03-28 10:45:23 INFO: ... 39 entries to add
2006-03-28 10:45:23 INFO: ... 0 entries to modify
2006-03-28 10:45:23 STATUS: test apply membdelete data against Scalix ...
2006-03-28 10:45:23 INFO: ... 0 entries passed for member.curr
2006-03-28 10:45:23 INFO: ... 0 entries failed for member.curr
2006-03-28 10:45:23 INFO: ... 0 entries warned for member.curr
2006-03-28 10:45:23 STATUS: test apply delete data against Scalix ...
2006-03-28 10:45:23 INFO: ... 0 entries passed for delete.curr
2006-03-28 10:45:23 INFO: ... 0 entries failed for delete.curr
2006-03-28 10:45:23 INFO: ... 0 entries warned for delete.curr
2006-03-28 10:45:23 STATUS: test apply add data against Scalix ...
2006-03-28 10:45:40 INFO: ... 39 entries passed for add.curr
2006-03-28 10:45:40 INFO: ... 0 entries failed for add.curr
2006-03-28 10:45:40 INFO: ... 0 entries warned for add.curr
2006-03-28 10:45:40 STATUS: test apply limit data against Scalix ...
2006-03-28 10:45:41 INFO: ... 0 entries passed for add.curr
2006-03-28 10:45:41 INFO: ... 0 entries failed for add.curr
2006-03-28 10:45:41 INFO: ... 0 entries warned for add.curr
2006-03-28 10:45:41 STATUS: test apply modify data against Scalix ...
2006-03-28 10:45:41 INFO: ... 0 entries passed for modify.curr
2006-03-28 10:45:41 INFO: ... 0 entries failed for modify.curr
2006-03-28 10:45:41 INFO: ... 0 entries warned for modify.curr
2006-03-28 10:45:41 STATUS: test apply limit data against Scalix ...
2006-03-28 10:45:41 INFO: ... 0 entries passed for modify.curr
2006-03-28 10:45:41 INFO: ... 0 entries failed for modify.curr
2006-03-28 10:45:41 INFO: ... 0 entries warned for modify.curr
2006-03-28 10:45:41 STATUS: test apply membadd data against Scalix ...
2006-03-28 10:45:42 INFO: ... 0 entries passed for member.curr
2006-03-28 10:45:42 INFO: ... 0 entries failed for member.curr
2006-03-28 10:45:42 INFO: ... 0 entries warned for member.curr
2006-03-28 10:45:42 STATUS: test apply membmodify data against Scalix ...
2006-03-28 10:45:42 INFO: ... 0 entries passed for member.curr
2006-03-28 10:45:42 INFO: ... 0 entries failed for member.curr
2006-03-28 10:45:42 INFO: ... 0 entries warned for member.curr
2006-03-28 10:45:42 INFO: test mode - keep current search result for
reprocessing
2006-03-28 10:45:42 STATUS: test LDAP dir sync import dslx01p completed
#############
2006-03-28 10:45:42 STATUS: test LDAP dir sync export dslx01p started
###############
2006-03-28 10:45:42 INFO: agreement type 13 only supports import operation
2006-03-28 10:45:42 STATUS: test LDAP dir sync export dslx01p completed
#############