You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I made PR #948 to fix this issue by generating a random base64 value for the password that's stored in the user's home directory config file on generation of the config 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.
The text was updated successfully, but these errors were encountered: