ql/
> Part 2:
>
http://www.xaprb.com/blog/2006/08/18/role-based-access-control-in-sql-part-2/
>
> This is for an SQL-based row-level authorization system, but it could be
> adapted to a graph-based node-level system.
>
> - James
>
> --
> View this message in context:
h
-access-control-in-sql-part-2/
This is for an SQL-based row-level authorization system, but it could be
adapted to a graph-based node-level system.
- James
--
View this message in context:
http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-Best-practice-for-User-Authentication-and-Auth
Brendan,
Is it OK to restrict different users based in ACL structures on Subgraph
level or on individual node level? The former probably would work with
traversal, the latter is probably a bit harder.
/peter
Sent from my phone.
On Sep 15, 2011 7:57 AM, "Brendan cheng" wrote:
>
> Hi,
> What desig
Hi,
What design pattern do you recommend for user authentication and authorization
in neo4j graph?I'm searching a simple and flexible way to restrict the access
to certain part of graph which is dynamically depends on the user and
role...etc.How to avoid excessive traversing?
Any idea is apprec
4 matches
Mail list logo