Roy, interesting use-case :-) I'm forwarding this to the user-list in case somebody wants to share some thoughts on the topic.
Short recap (Roy, please correct me if I'm wrong): we need a way to pre-configure a useradmin instance when starting up the container. I guess this results from the wish to avoid writing an UI to let some admin enter the data. You're right: currently the only way would be to use a preconfigured LDAP server and the LDAP provider. However, IMHO the 'clean way' would be to introduce a new useradmin command (e.g. useradmin import <file-name>) for that. That would be pretty straightforward to implement: just define a format (XML?) and code the import by using the standard OSGi Useradmin Service interface. I'm not really sure about having a configuration property that imports users from a given file (if they not already exist). @the pax gang: any opinions, more sophisticated solutions? Cheers, Matthias On Wed, May 9, 2012 at 10:34 AM, Roy Phillips <phillips....@gmail.com> wrote: > Hey Matthias, thanks for getting back to me and in my own language, sogar... > My deployment, following on from the hints on the Pax UserAdmin wiki, uses > felix.prefs, and digging into that, I found it stores any preferences set > (e.g., Users, Roles) in a binary format, for example: > ./runner/equinox/org.eclipse.osgi/bundles/109/data/P110_Pax UserAdmin.ser > - great for persistence, but kind of hard to pre-configure users and > roles... > I guess the LDAP provider is the way to go? > > thanks, roy > > On Sun, May 6, 2012 at 9:00 PM, Matthias Küspert <mkuesp...@googlemail.com> > wrote: >> >> Hi Roy, >> >> the Pax UserAdmin docs state: 'uses the same layout as the Equinox >> UserAdmin implementation'. That means that the layout of storing user >> admin data in the preferences is the same as used by the Equinox >> UserAdmin implementation (i.e. usage of nodes and subnodes of the >> Preferences Service). This has nothing to do with the layout that the >> Preferences Service uses to store its data on disk. I never had to >> dive into the Preferences Service implementation that far. >> >> Sorry that I cannot help here. You probably will have to refer to the >> source code of the Equinox Preferences Service to find out the >> details. >> >> Cheers, >> Matthias >> >> 2012/5/5 Roy Phillips <phillips....@gmail.com>: >> > Hi Matthias, >> > Apropos die Pax UserAdmin service - hast Du vielleicht eine Beispiel für >> > die >> > 'Preferences' Dateiformat (Users/Roles/...)? >> > >> > Nach den docs, es sollte gleiche wie das Equinox UserAdmin >> > implementation >> > sein, aber ich finde weder Spezifikation noch Beispiele dafür. >> > >> > BTW, ich bin bereit zu "participate", zum Beispiel, um die Documentation >> > verlängern, wenn das hilft... >> > >> > Vielen Dank im Voraus, roy > > _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
