You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Caching access token during BrowserIdcAuthPlugin authentication for subsequent/parallel session requests #265
Currently, running SQL queries via BrowserIdcAuthPlugin is done on a per-session basis. This can be tiresome when running queries across different sessions in parallel (e..g, dbt), where multiple browser pop-ups are triggered throughout the run duration. I would like to add a feature to cache the access token received during the token exchange process, so that future sessions will reuse the cached token instead of re-initializing a new session.
As the proposal involves storing the access token locally (whether it be via file/memory, plain-text/encrypted, etc.), would this be a security issue? Not sure if it would be a hard blocker before I open a PR for this feature proposal.
Reacted by Kyle Huston, gss2002, jernejg and MangoAndFish22
Activity
MangoAndFish22 commentedon Nov 27, 2025
I have logged a similar request on the Redshift ODBC driver page - for exactly the same thing but for AzureAD Oauth2.
The pop ups are super frustrating!