# ask-community

Martin Picard

01/12/2023, 4:08 PM
Hey folks, I am running into an issue with dagster-postgres on azure, we are using workload identities to authenticate and so the PGPASSWORD is a token that needs to be refreshed every ~60 minutes. Our current solution is to refresh the k8s secret and restart the deployment. We looked at the dagster-postgres code and it seems difficult to supply a refreshed token because it's given the full connection string. The other option would be to maintain a custom PostgresStorageClass but ideally we would like to maybe find a solution/create a PR that works in both scenarios (static and dynamic pgpasswords). Any tips?
👍 1
Also if someone can point me to the code where the postgres storage classes are instantiated I would be able to see how the connection string is built


01/13/2023, 4:30 PM
the storage components get instantiated with the
, usually at the beginning of any dagster related process
🌈 1

Martin Picard

01/19/2023, 12:54 PM
Thanks @alex!