feat(oauth-providers): Allow for refresh tokens to be used via access_type "offline" in Issue/#619

[aaronware]

I might need some support here as I wasn't able to figure out the most efficient way to test my changes based on how this all works within a worker? Any shove in the right direction would be greatly appreciated for proper testing.

[aaronware]

I also don't really understand why it had my other pull requests in the commit logs... No changes for those files are actually in this pull request

[aaronware]

Closes #619

[yusukebe]

Hi @aaronware

Thanks for the PR. I think it would be fine if you tested it with the npm link though we should add more test codes.

@monoald Do you have any thoughts on this?

[aaronware]

Thanks @yusukebe , I got pulled away from this onto some items but I should have some time over the next week to confirm it's all working properly within the worker. @yusukebe I'll keep an eye out for any recommendations/changes you or @monoald have and adjust the PR as needed

[Titou325]

Hi! We are also interested in this behaviour to configure long-running sessions (eg. polling GMail on behalf of a user). Right now the flow does not expose the refresh token (although it is received), but could very easily when correctly configured with prompt: "consent" and access_type: "offline".

It is hard to monkey patch at this time as this is internal to AuthFlow. I don't know if this PR is still under consideration or if I should open a new one to cover this use case.

[yusukebe]

Hi @Titou325

This PR is not progressing, so creating a new PR is okay. If so, I will review it. It would be better if you added proper tests there.

[freckletonj]

agreed, it'd be nice if we had support for google refresh tokens

[yusukebe]

Hi @aaronware

Can you still work on this PR? I think this feature is okay, but I want to do two things:

• Writing tests
• Update README.md

If these are done, I'll review them!

[aaronware]

@yusukebe I can pick this up again in the next week or so