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

Local permissions issue #223

Open
iulianolyn opened this issue Jan 24, 2024 · 0 comments
Open

Local permissions issue #223

iulianolyn opened this issue Jan 24, 2024 · 0 comments

Comments

@iulianolyn
Copy link

Hi everyone,

I just deployed the consensys Kubernetes in AWS and I'm struggling with activating the local permissions. So basically I would like to have accounts-allowlist=[] with a list of accounts that are allowed to do transactions on the nodes.

I've noticed that the permissions_config.toml is not mounted inside the volumes so I added the following configuration to the /helm/charts/besu-node/node-statefulset.yaml:

In volumes:

{{- if .Values.node.besu.permissions.enabled }}
      - name: permissions-config
        configMap:
          name: {{ include "besu-node.fullname" . }}-permissions
          items:
            - key: permissions_config.toml
              path: permissions_config.toml
{{- end }}

in volumesMounts:

{{- if .Values.node.besu.permissions.enabled }}
          - name: permissions-config
            mountPath: /config/permissions
            readOnly: false
{{- end }}

and then I updated the /helm/charts/besu-node/values.yaml with:

permissions:
      enabled: true
	filePath: "/config/permissions/permissions_config.toml"
      accounts:
        enabled: true
        allowlist: ["0x*********************************"]

Everything seems fine until I start the nodes. I get a warning like this:
TomlConfigFileParser | Write access denied for file at: /config/permissions/permissions_config.toml. Configuration modification operations will not be permitted.

I ssh into the pod validator by kubectl exec --stdin --tty -n besu besu-node-validator-1-0 -- /bin/bash and I checked the file and it has r/w permissions.
lrwxrwxrwx 1 root root 30 Jan 24 10:23 permissions_config.toml -> ..data/permissions_config.toml

besu@besu-node-validator-1-0:~$ cat /config/permissions/permissions_config.toml
# Permissioning TOML file

accounts-allowlist=["0x******************************"]
nodes-allowlist=[]

besu@besu-node-validator-1-0:~$

I tried also to publish a smart contract using the account from the allowlist and I got this issue from hardhat: Sender account is not authorized to send transactions. Just to mention that if I do not activate the permissions there is no issue publishing a smart contract.

Do you guys have an idea what is wrong with the configuration? Do you have any recommendations on how to activate local permissions?

Thank you!
Iulian

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

No branches or pull requests

1 participant