Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change Password Mechanism #772

Open
rstyd opened this issue Jan 30, 2024 · 3 comments
Open

Change Password Mechanism #772

rstyd opened this issue Jan 30, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@rstyd
Copy link
Collaborator

rstyd commented Jan 30, 2024

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.

@rstyd rstyd added the enhancement New feature or request label Jan 30, 2024
@aquan9 aquan9 assigned rstyd and unassigned aquan9 Oct 15, 2024
@aquan9
Copy link
Collaborator

aquan9 commented Oct 15, 2024

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.

@pagrubel
Copy link
Collaborator

pagrubel commented Dec 2, 2024

We had to revert the changes from this PR since it caused the issue reported in #959 so I'm re-opening this issue

@rstyd
Copy link
Collaborator Author

rstyd commented Dec 3, 2024

Need to additionally make sure we no longer hardcode the neo4j password in the integration test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants