Closed shazinahmed closed 3 years ago
Additional observation.
This gives me a result
❯ vault read github-cert-dev/roles/backend-role
Key Value
--- -----
algorithm_signer n/a
allow_bare_domains false
allow_host_certificates false
allow_subdomains false
allow_user_certificates true
allow_user_key_ids true
allowed_critical_options n/a
allowed_domains n/a
allowed_extensions permit-pty,permit-port-forwarding,login@github.com
allowed_user_key_lengths map[]
allowed_users *
allowed_users_template false
default_critical_options map[]
default_extensions map[permit-pty:]
default_user n/a
key_bits 0
key_id_format n/a
key_type ca
max_ttl 96h
ttl 48h
But this give me null
vaultTemplate.read("github-cert-dev/roles/backend-role")
I created another signing role and the application works with it. Looks like it is an issue with the backend than the spring-vault. Hence closing the issue.
I am currently using Spring Vault in my project for storing secrets in KV backend, authenticated using AppRole. That works well.
Now, I am trying to add SSH key signing capability in the app. Even though I am able to create certificates using the CLI, doing it through spring-vault gives me 400 errors. Below are the details.
Over CLI (using same role-id and secret-id):
Now if I try to do the same programatically. I get the below error:
Below is the relevant code:
The POJO used:
The version:
Am I doing something wrong here? Please let me know if you need more details.
Thank you!