Alternatively you could try using container-based authentication, and script user provisioning using the application server's available tools. For example , the create-file-user command in Payara/GlassFish might do the trick (https://docs.oracle.com/cd/E26576_01/doc.312/e24938/create-file-user.htm#GSRFM00024). Container-based authentication using LDAP could be another approach. If you're deploying in a corporate environment with a growing number of users, either option might be a more manageable approach going forward.
-- Dave Koelmeyer http://blog.davekoelmeyer.co.nz GPG Key ID: 0x238BFF87 The Document Foundation (TDF) member On Fri, Aug 4, 2017, at 02:31 AM, Lance Bader wrote: > Can anyone tell me how to provision a collection of new wiki users? > > In our corporate wiki, we do not allow self provisioning. I have > configured the policies so that the only page that un-authenticated users > can view is the logon page. Up to this point, I have been using the > admin pages to add new users (even though they are ugly, counter > intuitive, and cannot be used to modify or delete a user). Now we are > going through a growth spurt and I don't want to use the admin panels to > add each wave of new hires. > > The organization of WEB-INF/userdatabase.xml is clear enough, but I need > hints on how to populate the uid and password attributes. If I remember > correctly, back in the pre-Apache JSPWiki, there was a special encoding > that could be used which, when read by JSPWiki, would be converted and > replaced with the canonical form. I would be forever grateful if someone > could tell me how to do that in JSPWiki v2.10.2. > > Lance
