Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 3.2.2.ER3, 3.2.6-Ghost.GA
Affects Version/s: 2.13.7.GA
Component/s: reactive-pg-client, team/eng
Labels:
None

Steps to Reproduce:

Hide

https://github.com/senthilredhat/quarkus-reactive/tree/Custom-Credentials-Provider
This reproducer uses Custom Credential Provider Implementation showcasing the issue we noticed in Vault. (https://quarkus.io/guides/credentials-provider#custom-credentials-provider )

The setup and replication instructions are available at https://github.com/senthilredhat/quarkus-reactive/blob/Custom-Credentials-Provider/reactivequarkusorderservice/setup-running.md

Show
https://github.com/senthilredhat/quarkus-reactive/tree/Custom-Credentials-Provider This reproducer uses Custom Credential Provider Implementation showcasing the issue we noticed in Vault. ( https://quarkus.io/guides/credentials-provider#custom-credentials-provider ) The setup and replication instructions are available at https://github.com/senthilredhat/quarkus-reactive/blob/Custom-Credentials-Provider/reactivequarkusorderservice/setup-running.md
[QE] How to address?:
---

Description

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.

Attachments

Issue Links

links to

RHSA-2023:120897 Red Hat build of Quarkus 3.2.6 release and security update

Activity

People

Assignee:: Thomas Segismont

Reporter:: Senthil Palaniswamy

Tester:: Fedor Dudinskii

Votes:: 1 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: 2023/03/08 7:46 PM

Updated:: 2023/11/09 4:19 PM

Resolved:: 2023/08/28 1:41 PM