multiple users + db

[f1-outsourcing]

I mostly installed the dozer plugin so it is easier to have access to different databases at once. However I currently have to test with two different clients and prefer this testing to be done on their specific test data set.

How do I go about creating an environment where userA is able to only access dbA and userB is able to only access dbB?

[f1-outsourcing]

#33

[jmsuhy]

This will be part of the security updates we are adding. We have been discussing if we want to follow Neo4j's approach and implement security same way - or go with a more robust and configurable approach leveraging OPA integration with Apache Shiro that would be configuration based without corresponding cypher commands.

If you have any ideas, let me know. Also - I will create a discussion for this so the community can chime in.

[f1-outsourcing]

Ohhh what a question :) I am not really into design and development with Neo4j. I assume the approach of neo4j is to have database roles and users and some privileges on these roles. I also had to lookup this Shiro which looks interesting especially since I have some springboot neo4j api. Currently I am making some work-a-round to store users in the database so I am more flexible adding new users and tracking the objects they created. I think the Shiro / OPA approach would be much more flexible in this regard, on the other hand sticking to 'standard compatibility' also has its advantages. Although I have the impression that currently everyone is more or less forced to build middle ware because of these user limitations.

[jmsuhy]

The system database is used for storing users, etc - so we can implement the base functionality of managing users and roles there as a first step.

[f1-outsourcing]

Yes for me this would be ideal for my current testing. I am now testing in different stages of the application development and I need different data for this and I also do not want to mix data to keep things simple and understandable. So to make sure developers are using their correct environment a user per database would be perfect.