From: Adam R. <ad...@ex...> - 2013-01-15 18:11:59
|
As Dannes said, access control in eXist is at a Document and/or Collection level. If you want to do node level access, then you are on your own somewhat. You could try XACML but I do not know if this still works in eXist, its almost certainly unsupported. In your place, I would probably force access to the documents through a XQuery/XSLT that performs an identity transform on the source document, removing any nodes that the current user is not authenticated to see. You could keep a list of users and elements that are not permitted for those users in a separate config document of your own devising. On 12 January 2013 16:55, Ihe Onwuka <ihe...@gm...> wrote: > The users in my app may have access to documents but the elements > they can see in those document are to be restricted by permissions > attached to their user id. > > So it would seem that my requirement is for a more finely grained > access control mechanism than ACL 2.0 allows. > > > On Sat, Jan 12, 2013 at 4:35 PM, Dannes Wessels <da...@ex...> wrote: >> Meaning: use the new ACL's as introduced in 2.0 >> >> On 12 Jan 2013, at 17:19 , Dannes Wessels <da...@ex...> wrote: >> >> XACML is not the way to go in eXist-db anymore, it is kind of deprecated; >> i'd suggest to do things different.... >> > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122912 > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |