Hello:
I recently ran into a race condition that I am requesting a fix for. Describing the use case:
Our java client uses temp credentials (dynamic user) generated via the vault-atlas plugin for db authentication - (it is a short term lease for 1d). We are facing an issue where the user creation takes a few seconds but then the temp credentials are already returned back by the client. So when our code tries to authenticate -- the user is not there in atlas and we get an Auth Exception. Whereas if we put a sleep time, and allow for the user to be created, then we can authenticate fine.
We expect the plugin to wait until user is created before it returns the credentials - we dont run into this race condition.
Hello:
I recently ran into a race condition that I am requesting a fix for. Describing the use case:
Our java client uses temp credentials (dynamic user) generated via the vault-atlas plugin for db authentication - (it is a short term lease for 1d). We are facing an issue where the user creation takes a few seconds but then the temp credentials are already returned back by the client. So when our code tries to authenticate -- the user is not there in atlas and we get an Auth Exception. Whereas if we put a sleep time, and allow for the user to be created, then we can authenticate fine.
We expect the plugin to wait until user is created before it returns the credentials - we dont run into this race condition.