[ http://issues.apache.org/jira/browse/DIREVE-264?page=all ]

Stefan Zoerner updated DIREVE-264:
----------------------------------

    Attachment: apache.ldif

In order to illustrate the LDIF idea, here is an example. It contains 128 
person entries (inetOrgPerson) for the current ASF members. Alex has DN 
uid=alex,ou=people,dc=apache,dc=org, for instance.
I used HttpUnit to fetch the data from the page mentioned above. For the uid I 
have chosen the firstname. If not unique I appended a number (e.g. daniel2). 
Currently, only a few attributes are used (sn, cn, givenname, initials, 
labeledUri, uid).

Next steps would be: 
* add groups for the different roles within ASF 
* add groups for all projects (TLPs)
* fill groups with appropriate members
* add user passwords (e.g. in order to demonstrate Tomcat integration)
* add some JPEG photographs, if some members agree (to demonstrate binary data)

Maybe, we can place the finished file in a demo folder of the standalone ZIP 
build.

This is just for demonstration. Any ideas and feedback are welcome. Especially 
whether you think this is useful. If so, I will enhance/finish it.

> Standalone build should be available for 0.9.3
> ----------------------------------------------
>
>          Key: DIREVE-264
>          URL: http://issues.apache.org/jira/browse/DIREVE-264
>      Project: Directory Server
>         Type: Improvement
>     Versions: 0.9.3
>     Reporter: Nick Faiz
>     Assignee: Alex Karasulu
>  Attachments: apache.ldif
>
> We need to identify the documentation which should be included in the 
> standalone build. We also need to work out how the standalone argument should 
> be used in the current release build script.
> The current maven standalone goal, in main, can be leveraged for this purpose.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to