From: Dmitriy S. <sha...@gm...> - 2010-09-11 15:20:53
|
Hello, the commit http://exist.svn.sourceforge.net/exist/?rev=12690&view=rev should fix both issues. Let me know any result you get. -- Cheers, Dmitriy Shabanov On Thu, 2010-09-09 at 13:24 +0500, Dmitriy Shabanov wrote: > I on a way to commit fixes for group and after will test possible > information lost after restart. > > On Thu, 2010-09-09 at 06:10 +0545, Chris Tomlinson wrote: > > Hello, > > > > I am puzzled about the security rework and I assume I am missing something. > > > > It looks to me like changes that are made through the java client are not retained across restarts of eXist. I am testing trunk revision 12655 on Mac OS/X 10.6.4. I am using the java client in the build of trunk. > > > > I have built the DB by restoring from a previous backup which includes a users.xml. After the restore the various users appear without their group associations in the users collection but I can not log in as any except the admin user. > > > > If I then follow a suggestion to use the java client and fetch and store back the users.xml then indeed the converter appears to run and I can then login via various users and passwords as would be expected UNTIL I restart the DB and then everything is fogotten. > > > > Also if I add a group via the java client the group is not remembered. > > > > If I manually add a group document to the groups collection then it appears in the list of possible groups but if I assign the group to a user via the java client and restart the DB then the assignment is not retained. > > > > What is the correct procedure to migrate users and group assignments to the new scheme? > > > > Also how is group membership represented in the new scheme please? I can't see how there is any association of groups with users like in the old scheme. There just seem to be a list of users with no group associations and a list of groups with no user associations. > > It should be same, need to finish refactoring. The groups staff is last > todo in the list. > |