[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Syncrepl nits with operational attributes (ITS#3289)

lukeh@padl.com wrote:

>Full_Name: Luke Howard
>Version: 2.2.15
>OS: Linux
>URL: ftp://ftp.openldap.org/incoming/
>Submission from: (NULL) (
>It seems to me that, when using syncrepl,
>creatorsName/createTimestamp/modifiersName/modifyTimestamp should be
>Also, attempting to synchronize all operational attributes with attrs="*,+"
>results in bogus data (note the duplicate operational attributes):
># Kurt Zeilenga, Users, dsg.padl.com
>dn: cn=Kurt Zeilenga,cn=Users,dc=dsg,dc=padl,dc=com
>structuralObjectClass: inetOrgPerson
>creatorsName: cn=administrator,cn=users,dc=dsg,dc=padl,dc=com
>createTimestamp: 20040818123004Z
>entryCSN: 20040818123627Z#000001#00#000000
>modifiersName: cn=krbtgt,cn=users,dc=dsg,dc=padl,dc=com
>modifyTimestamp: 20040818123627Z
>subschemaSubentry: cn=Aggregate,cn=Schema,cn=Configuration,dc=dsg,dc=padl,dc=com
>hasSubordinates: FALSE
>entryUUID:: E4VgWoVeECiExunRNTOduQ==
>subschemaSubentry: cn=Aggregate,cn=Schema,cn=Configuration,dc=dsg,dc=padl,dc=com
>hasSubordinates: FALSE
>This should probably be handled somehow.
I agree, although I don't have any favored approach here.

For the moment you can just explicitly list 
creatorsName/CreateTimeStamp/etc in the syncrepl attrs, and omit 
anything else.
Perhaps we need to add a "attrs=!foo" config syntax to strip certain 
attributes from the incoming records. I don't really like this approach 
because it requires too much manual intervention.

Maybe better would be for syncrepl to have a hardcoded list of 
attributes that it ignores - e.g., all values that we know are 
dynamically generated (like hasSubordinates) and all values that are 
DSA-specific (e.g. subschemaSubentry), so that attrs=*,+ will work 
without hassles.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support