I agree, such functionality would be nice. I thought I might start taking a look into what was started with security so far and maybe do some work on it. Is there anyone actively working on/in charge of this section? Here are my thoughts so far on the security.

1. Support of user authentication entities (i.e. userid/passwd to connect)
2. Support user/group authorization entities (i.e. these users, or members of these groups, can connect, read, write, etc)
3. Support multiple back stores for this data (the current work uses an XML file, it would be nice to have LDAP and Database support as well)
4. Support restrictions on the following:
- create, query, update, remove, create XMLObject, remove XMLObjects, create Indexes, remove Indexes for collection
- Connect, create collection, remove collection for databases.


At 01:50 PM 1/15/2002, you wrote:
I see in the source code that you are working on user/group security and read and write access. One powerful feature would be to add xpath based security. By allowing a user or group read/write access to a specific xpath in a collection or document.

<person>
     <name>John Doe</name>
     <salary>1000</salary>   <- no access
</person>

---- not real -  access xml doc ---
<group>
     <user id="bigboss">
        <access>
               <collection id="documents">
                    <xpath>//salary</xpath>
                    <privileges>none</privileges>
               </collection>
          </access>
     </user>
</group>

This is just a quick example - an a final suggestion.

What do you think?

Regards, Niels Peter



Reply via email to