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

After changing the data directory for nethermind client, default jwt secret is still generated in default directory. #7746

Open
obasekiosa opened this issue Nov 11, 2024 · 2 comments · May be fixed by #7765

Comments

@obasekiosa
Copy link
Contributor

Description
In the absense of jwt-secret file and a change in default data directory, jwt-secret file is still generated in default data directory.

Note:
check for similar behaviour if data directory is specified using env or config file.

Steps to Reproduce
In order to replicate the behavior, please provide a detailed list of steps:

  1. change the default data directory using --dd <new_data_dir>
  2. delete previous jwt-secret
  3. ensure jwt-secret is not specified in config file or as config parameter (so it gets auto generated)

Actual behavior
jwt-secret file is generated in src/Nethermind/Nethermind.Runner/keystore.

Expected behavior
jwt-secret file should be generated in <new_data_dir>/keystore

@ssonthal
Copy link
Contributor

Hey @obasekiosa , can you check if the linked PR addresses the issue.

@ssonthal ssonthal linked a pull request Nov 18, 2024 that will close this issue
16 tasks
@mimisavage
Copy link

Can I take care of this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants