Currently I have a website which uses MS SQL 2008 and the Microsoft Membership Provider to create/authenticate users, this works fine. We have migrated all of our 'data' over to Neo4j, which has gone really well and everything works, but we are not sure at this point the best way of managing the authentication system.
So the question is, what is the standard way to store/retrieve credentials and other sensitive information and perform authentication using a graph database. Is it ideal to store the credentials data in the graph, or should we still use MSSQL and the Membership provider we already have?
The authentication feature introduced in Neo4j 2.2 is just a "all or nothing" based on username / password.
If you need a more fine grained approach you need to implement your own security rules.