[
https://issues.apache.org/jira/browse/DIRAPI-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360424#comment-14360424
]
Emmanuel Lecharny commented on DIRAPI-225:
------------------------------------------
We can default with a list of attributes that are to be anonymized, no matter
what :
* userPassword
* displayName
* givenName
* surName
* homePhone
* homePostalAddress
* jpegPhoto
* labeledURI
* mail
* manager
* mobile
* organizationName
* pager
* photo
* secretary
* uid
* userCertificate
* userPKCS12
* userSMIMECertificate
* x500UniqueIdentifier
* carLicense
* host
* locality
* organizationName
* organizationalUnitName
* seelAlso
* homeDirectory
* uidNumber
* gidNumber
* commonName
* gecos
* description
* memberUid
> Add a LDIF anonymizer that takes a LDIF file and replace the value with
> random text
> -----------------------------------------------------------------------------------
>
> Key: DIRAPI-225
> URL: https://issues.apache.org/jira/browse/DIRAPI-225
> Project: Directory Client API
> Issue Type: Improvement
> Affects Versions: 1.0.0-M28
> Reporter: Emmanuel Lecharny
> Fix For: 1.0.0-M29
>
>
> From time to time, we have to ask for user's LDIF, or users have to transmit
> LDIF to someone else for test purposes. It's clearly important to be able to
> have anonymized files, so that no critical information is leaked.
> The idea would be to read the original LDIF, replacing all teh values with
> random - but syntaxically correct - values.
> It should also be configurable (ie, the list of attributes to anonymized
> should be extensible).
> We have to take care of DN too, and of attributes which are DN pointing on
> some of the base entries (like Member).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
