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

Error Parsing Seal Configuration in OCI #13664

Open
nvkanumuri opened this issue Jan 14, 2022 · 2 comments
Open

Error Parsing Seal Configuration in OCI #13664

nvkanumuri opened this issue Jan 14, 2022 · 2 comments

Comments

@nvkanumuri
Copy link

nvkanumuri commented Jan 14, 2022

I am trying to setup vault on OCI Instances with HA enabled. This is how my config looks like..

api_addr = "http://127.0.0.1:8200"
cluster_name = "vault"
default_lease_ttl = "5m"
listener "tcp" {
address = "0.0.0.0:8200"
#tls_cert_file = "/etc/vault.d/vault.crt"
tls_disable = "true"
#tls_key_file = "/etc/vault.d/key.pem"
}
log_level = "DEBUG"
max_lease_ttl = "30m"

seal "ocikms" {
auth_type_api_key = "false"
crypto_endpoint = "<crypto endpoint of vault"
key_id = ""
management_endpoint = "mgmt end point of vault
}

storage "oci" {
auth_type_api_key = "false"
bucket_name = "vault"
ha_enabled = "true"
lock_bucket_name = "vault_lock"
namespace_name = "idoll6i6jmjd"
}

ui = "true"

When I try to start vault service I see this error in logs. I created dynamic group and vault policies in root compartment and added policy also to allow to access bucket from root's child compartment.. Can someone please help with it?

Jan 14 06:25:59 inst-i9dhe-vault-1 sh[186118]: Error parsing Seal configuration: failed key_id validation: error encrypting data: Service error:NotAuthorizedOrNotFound. Key or Vault does not exist or you are not authorized to access them.. http status c>
Jan 14 06:25:59 inst-i9dhe-vault-1 systemd[1]: vault.service: Main process exited, code=exited, status=1/FAILURE
Jan 14 06:25:59 inst-i9dhe-vault-1 systemd[1]: vault.service: Failed with result 'exit-code'.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Run vault write ...
  2. Run vault login....
  3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Environment:

  • Vault Server Version (retrieve with vault status):
  • Vault CLI Version (retrieve with vault version):
  • Server Operating System/Architecture:

Vault server configuration file(s):

api_addr = "http://127.0.0.1:8200"
cluster_name = "vault"
default_lease_ttl = "5m"
listener "tcp" {
  address       = "0.0.0.0:8200"
  #tls_cert_file = "/etc/vault.d/vault.crt"
  tls_disable   = "true"
  #tls_key_file  = "/etc/vault.d/key.pem"
}
log_level = "DEBUG"
max_lease_ttl = "30m"

seal "ocikms" {
  auth_type_api_key   = "false"
  crypto_endpoint     = "<crypto endpoint  of vault"
  key_id              = "<correct key ocid>"
  management_endpoint = "mgmt end point of vault
}

storage "oci" {
  auth_type_api_key = "false"
  bucket_name       = "vault"
  ha_enabled        = "true"
  lock_bucket_name  = "vault_lock"
  namespace_name    = "xxxxxxxxx"
}

ui = "true"

Additional context
Add any other context about the problem here.

@hsimon-hashicorp
Copy link
Contributor

Hi there! What version of Vault are you using?

@nvkanumuri
Copy link
Author

Hi, I am using 1.4.1 version

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

No branches or pull requests

2 participants