hgarrow

I have set up a single node vault instance and the plugin is operating correctly. My earlier install was a vault raft 3-node cluster. I will need to stand up...

At debug logging in vault, This is all that I see after enabling the plugin. I also am unable to write the config file, and this is the version plugin...

This was built from v1.0.0 branch https://github.com/1Password/vault-plugin-secrets-onepassword vault version 1.7.1-1 golang from epel version 1.15.5-1.el7 sha256sum /etc/vault.d/vault_plugins/op-connect |cut -d ' ' -f1 c7feaa260b5724fce0032b8a61a7dc061f51e1e000426549610ada1b582475ce /etc/vault.d/op-connect-config.json ``` { "op_connect_host": "http://OnePa-LoadB-....elb.us-east-1.amazonaws.com:8080", "op_connect_token": "reallylongprivatestring"...

For the Raft implementation, mlock is disabled. I did use setcap against the binary on all three servers in the raft cluster and restarted vault, registering and creating a new...

I will admit, some of those earlier errors(#9) happened while we were attempting to get the connector docker containers working properly. The specific 403 error I am no longer seeing,...

No, I was unable to resolve this issue. I have not looked into the integration any further on my side, as the Hashicorp Raft configuration is integral to our use...