As stated at Black Hat there is currently a kind of safe mode in the UI that prevents people from messing with the Neo4j db in order to update properties etc. from the BHCE UI. This was a design decision to protect enterprise customers from destroying their persistent databases afaik.
Current Behavior:
No write access to DB for no/any user role.
Desired Behavior:
The Admin user and certain roles should be able to update stuff in neo4j from the UI via cypher queries without having to connect to the db directly.
Use Case:
As consultants our use of the neo4j db is quite temporary. There is no need to protect us from ourselves in this case.
Implementation Suggestions:
You could add it to the role model or add a ENV var to the docker-compose definition file.
Feature Description:
As stated at Black Hat there is currently a kind of safe mode in the UI that prevents people from messing with the Neo4j db in order to update properties etc. from the BHCE UI. This was a design decision to protect enterprise customers from destroying their persistent databases afaik.
Current Behavior:
No write access to DB for no/any user role.
Desired Behavior:
The Admin user and certain roles should be able to update stuff in neo4j from the UI via cypher queries without having to connect to the db directly.
Use Case:
As consultants our use of the neo4j db is quite temporary. There is no need to protect us from ourselves in this case.
Implementation Suggestions:
You could add it to the role model or add a ENV var to the docker-compose definition file.