You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Nick Burch (JIRA)" <ji...@apache.org> on 2016/05/30 14:53:12 UTC

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

     [ https://issues.apache.org/jira/browse/INFRA-12008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Burch updated INFRA-12008:
-------------------------------
    Attachment: dates.ldif

> 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)