Closed fercam24 closed 3 years ago
The sample above is a bit hard to understand. Can you provide a reproducer so we can look into the issue? Don't worry about the actual database. Having a Postgres or MySQL connector should be sufficient to let us the rest work out.
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.
@fercam24 Did you figure out what caused the "400 Bad Request: lease not found" exceptions? I am facing the same, although it gets printed as a WARN message. But it pollutes the logs with stacktraces.
Describe the bug When using rotation of credentials I receive a
Actually the rotation happens (with some delay. Don't actually understand why) but I always get this exception. Another thing is that I'm not sure to understand why the RequestedSecret has mode RENEW and when we ask for rotation we keep using mode ROTATION. Is there an impact on the behaviour?
If we look in the logs it starts with
then it expires so we request a ROTATE
Right after we get a newly created lease with ROTATE mode and we update the database credentials
Then happens a renewal, and at the second one it has rotated the secrets again the secret (looking at leaseId)
and then the previous one on renewal gets the exception. And it only happens after a rotation.
any idea?
Sample Here is the Configuration I use for renewal ` @Flogger @Configuration @ConditionalOnBean(SecretLeaseContainer.class) @ConditionalOnProperty( name = "titan.producer.scheduling.enabled", havingValue = "true", matchIfMissing = true) public class VaultConfiguration {
} `
my bootstrap.yml config
spring.cloud.vault: enabled: true discovery: enabled: false fail-fast: true authentication: APPROLE kv.enabled: false generic.enabled: false database: enabled: true role: datasource_${TITAN_PRODUCER_ENVKEY}-${TITAN_PRODUCER_GAMEKEY}_titan_${spring.application.name} username-property: spring.datasource.username password-property: spring.datasource.password config: order: -10 lifecycle: enabled: true lease-endpoints: SysLeases connection-timeout: 5000 read-timeout: 15000
The role in vault has a default_ttl of 60s and max_ttl of 6m (for testing purposes)
Debug logs