When a user log in through dex into Google, dex should be able to refresh the user's info with Google when client of dex refreshes it's id_token.
This is complicated because Google only allows a single refresh token out per client <-> end user pair, so we'd have to store connector data in our "offlinesessions" object globally, instead of in the refresh data like we do now.
Also is this general enough to do for all oidc providers, or just Google? Investigate.
When a user log in through dex into Google, dex should be able to refresh the user's info with Google when client of dex refreshes it's id_token.
This is complicated because Google only allows a single refresh token out per client <-> end user pair, so we'd have to store connector data in our "offlinesessions" object globally, instead of in the refresh data like we do now.
Also is this general enough to do for all oidc providers, or just Google? Investigate.