Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when no refresh_token is available #162

Closed
espen opened this issue Sep 5, 2022 · 1 comment
Closed

Error when no refresh_token is available #162

espen opened this issue Sep 5, 2022 · 1 comment

Comments

@espen
Copy link

espen commented Sep 5, 2022

Mailchimp only uses access_token and does not give a refresh_token. Currently it seems like omniauth-oauth2 requires refresh_token as it will check for it when access_token is assumed to be expired.

I have set option :auth_token_params, {:expires_at => 10.minutes.from_now} to avoid this but it seems like not the best solution. Is there any way to tell omniauth-oauth2 that no refresh_token should be expected? Or perhaps this could be added as an option on the strategy instead of setting expiry?

See stevenkaras/omniauth-mailchimp#8

@espen
Copy link
Author

espen commented Sep 5, 2022

Sorry, duplicate of #143

@espen espen closed this as completed Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant