-
Bug
-
Resolution: Done
-
Major
-
2.13.7.GA
-
None
-
False
-
None
-
False
-
-
---
-
-
We are implementing a reactive, quarkus application using the Postgres database with credentials from the Vault. In addition, we are trying to use the Credentials Provider model(https://quarkus.io/guides/credentials-provider) to fetch the credentials from Vault.
We noticed the reactive pool implementation gets the database credentials from the credential provider at the startup and uses the cached version through the application lifecycle. The connection pool does not use the rotated credentials when creating a new connection causing the application to fail.
- links to
-
RHSA-2023:120897 Red Hat build of Quarkus 3.2.6 release and security update