We need to change the way passwords are handled in Neo4J (if we choose to stick with it). Currently passwords are set in the configuration file and used in start_gdb. I propose we modify this to create an authorization code file when beeflow first starts then the configuration file will have the path to this file.
We need to change the way passwords are handled in Neo4J (if we choose to stick with it). Currently passwords are set in the configuration file and used in start_gdb. I propose we modify this to create an authorization code file when beeflow first starts then the configuration file will have the path to this file.