[jira] [Commented] (INFRA-12008) Correcting LDAP createTimestamp for pre-200905 accounts

["Sam Ruby (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-12008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306751#comment-15306751 ] 

Sam Ruby commented on INFRA-12008:
----------------------------------

When I try I get

modifying entry "uid=rubys,ou=people,dc=apache,dc=org"
ldap_modify: Invalid syntax (21)
	additional info: createTimestamp: value #0 invalid per syntax

Adding a 'Z' to the end of the timestamp gets me to:

modifying entry "uid=rubys,ou=people,dc=apache,dc=org"
ldap_modify: Constraint violation (19)
	additional info: createTimestamp: no user modification allowed

> Correcting LDAP createTimestamp for pre-200905 accounts
> -------------------------------------------------------
>
>                 Key: INFRA-12008
>                 URL: https://issues.apache.org/jira/browse/INFRA-12008
>             Project: Infrastructure
>          Issue Type: Task
>          Components: LDAP
>            Reporter: Nick Burch
>         Attachments: dates.ldif
>
>
> Currently, the earliest {{createTimestamp}} in LDAP is 20090519, which corresponds with when the full LDAP import happened. This is problematic for things like the {{projects.a.o}} timeline + {{accounts-evolution.json}} data, and for the ComDev locations map over time.
> Using the {{[NOTICE] Account created}} messages from the private mail archives, it is possible to work out creation dates for many accounts, and set an earlier dummy date for the very old ones.
> The attached ldif modify file will set actual creation dates for accounts created between early July 2004 and 19th May 2009 (earliest "valid" date currently), and set all pre-existing ones to the 1st July 2004 (to give a slightly more accurate default)
> Could you please sanity check this, then apply with ldapmodify?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)