The first thing that comes to mind is permissions. Are you logged in as an administrator when you look at the users and groups? Not all users have READ_SECURITY and/or WRITE_SECURITY permissions.
Essentially, if you were to have an SQL-based backend for persistance, you could look at the tables governing access control (acls, users, groups, user2group, group2group) and get your answer. When you configure Nuxeo to use LDAP for groups and users those tables are discarded and it now looks to LDAP for that information. I've never set up virtual-groups, but perhaps your LDAP is improperly set up? Are you using the example files from Nuxeo's public svn (default-ldap-users-directory-bundle.xml, default-ldap-groups-directory-bundle.xml, default-virtual-groups-bundle.xml)? There's a few .LDIF files included in svn with these contribution bundles (default-ldap-users-directory-bundle.xml, etc., etc), that you should be able to use to set up your LDAP and test to see if you're having the same problems when you use the default .LDIF files with the default contribution bundles. Most LDAP implementations come with a UI front end that allows you to insert an .LDIF file straight into the server. Another thing I've noticed while playing with pgAdmin when Nuxeo's running on Postgres is that the group2group table is not logically correct because the code inside Nuxeo makes the "parentGroupId" the child group of the "childGroupId" for some reason. Hope some of this helps. Good Luck. -- Posted by "darthwes" at Nuxeo Discussions <http://nuxeo.org/discussions> View the complete thread: <http://www.nuxeo.org/discussions/thread.jspa?threadID=2560#7120> _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
