spring-cloud / spring-cloud/spring-cloud-config

Support TLS authentication to HashiCorp Vault secrets

Open
#1,240 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
2k
Forks
1.3k
Avg merge
2d 59m
Merged PRs (30d)
16

Description

We have a customer that recently attempted to use mTLS configuration for their HashiCorp Vault when using it as a backend for Spring Cloud Services (SCS) Config Server. Here is what they provided as information about the attempted configuration:

Here is a link to cert auth at Vault:

https://www.vaultproject.io/docs/auth/cert.html

The bottom of the page has the link to the API.

I have gone through most of the process but am having MTLS issues as our dev vault instance currently has a self-signed cert.  Disabling the check also essentially disables the MTLS handshake.  The internal Vault team is going through the process right now to install a real cert.  They say they can successfully get tokens from Cert auth.

We don't currently support this option that I know of (please let me know if I'm incorrect?). Could we add configuration options that would setup the mTLS handshake and then Config Server would be able to access the Vault API once authorized?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Config Server Vault backend and its existing connection configuration, then review the Vault cert-auth API linked in the issue. Done means configurable client certificates and trust settings establish the requested mTLS connection to the Vault API, including the self-signed-certificate case.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring, spring-boot
Domain
api, authentication, backend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.