Spring Vault集成后读取密钥返回Null问题求助

Hey there! Let's work through why you're getting a null value when trying to fetch your JWT secret from Vault. You've already got the connection sorted, so we just need to tweak a few configuration details to get the secrets loading correctly.

First, Let's Verify Property Mapping & Vault Storage #

Looking at your setup:

• You stored the secret with vault kv put secret/spring-vault-config secret.jwt=123456789
• Your VaultConfig uses @ConfigurationProperties("secret") with a private String jwt

This mapping should work in theory (it targets the secret.jwt property from Vault), but let's confirm if Spring Cloud Vault is actually pulling that property into your application environment. Add a quick check using the Environment bean to verify:

@Autowired
private Environment env;

@Override
public void run(String... args) throws Exception {
    log.info("----------------------------------------");
    log.info("Configuration properties");
    log.info("secret.jwt from Environment: {}", env.getProperty("secret.jwt"));
    log.info(" the secret key for jwt is {}", vaultConfig.getJwt());
    log.info("----------------------------------------");
}

• If env.getProperty("secret.jwt") also returns null: Spring Cloud Vault isn't loading the secret from Vault at all.
• If it returns the correct value: The issue is with @ConfigurationProperties binding—double-check that Lombok's @Data is generating the getter correctly (you can manually add public String getJwt() to test this).

Fix Spring Cloud Vault Configuration #

Update your application.properties to explicitly configure the KV backend and ensure it targets your application's config path:

spring.application.name=spring-vault-config
spring.cloud.vault.token=00000000-0000-0000-0000-000000000000
spring.cloud.vault.scheme=http
spring.cloud.vault.kv.enabled=true
# Explicitly set KV backend (default is "secret") and version (dev server uses v2 by default)
spring.cloud.vault.kv.backend=secret
spring.cloud.vault.kv.version=2
# Ensure we load config from the application-specific path
spring.cloud.vault.config.enabled=true
spring.cloud.vault.kv.default-context=spring-vault-config

Optional: Use Bootstrap Configuration (Recommended for Spring Cloud) #

Spring Boot 2.4+ disables the bootstrap context by default, which is the standard way to load cloud configs like Vault early in the application lifecycle. To enable it, add this dependency to your pom.xml:

<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-bootstrap</artifactId>
</dependency>

Then move your Vault configuration from application.properties to bootstrap.properties—this ensures Vault settings are loaded before other application configs, preventing binding issues.

Simplified Test Alternative #

If you want to simplify for testing, adjust your Vault write command to remove the secret. prefix:

vault kv put secret/spring-vault-config jwt=123456789

Then update your VaultConfig to match the direct key name:

@Data
@ConfigurationProperties(prefix = "")
public class VaultConfig {
    private String jwt;
}

Final Checks #

• Confirm you have the spring-cloud-starter-vault-config dependency in your project (it's required for Spring Vault integration).
• Verify Lombok is working: Enable annotation processing in your IDE to ensure @Data generates getters/setters automatically.

Give these steps a try, and your secret should load correctly instead of returning null!

内容的提问来源于stack exchange，提问作者Thinh Pham