Hi folks, I just added a LDAP provider and streamlined the integration tests. Each integration test is run with a fresh instance of an ApacheDS server - for that purpose I wrapped ApacheDS in the pax-ldapserver-apacheds bundle available at:
https://scm.ops4j.org/repos/ops4j/laboratory/users/mkuespert/ldapserver/ The integration tests are not yet complete ... feel free to play around with the code and create some more :-) BTW: are there any Alliance members around which are able/allowed to run the TCK tests on the UserAdmin? That sure would help to spot the things I missed. The LDAP provider is based on objects available in the core.schema, however one problem remained open: how can members of groups hold an additional type (required/basic) as defined by the UserAdmin spec in 107.8.3? I'm currently pondering whether we should introduce a new UserAdmin schema or go on trying to do everything with the objectClasses from the core.schema - however, I'm not really into LDAP and schema design - any LDAP experts around who could shed some light on the implications? The final question for now is: how to proceed? I already got some initial agenda/questions: - code: -- anybody volunteering to do some code review? -- how to get it under the official Pax umbrella? - documentation ... yes I know ... will start something in my personal space soon - legal: the preferences provider and some service code is inspired from the Equinox UserAdmin - do we need to/should we mention that somewhere? Just in a README or more formal in the license header? Cheers, Matthias
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
