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
@espen Thanks for sharing your solution. It works for me, though I use a 1 year expiry which is plenty in my case. In general, using .year.from_now won’t work for this library though I’d presume as it relies on ActiveSupport extensions to Integer. Other than that I’m not sure either whether there’s a better way. Looking at the Ruby example for Mailchimp’s OAuth2 flow (https://mailchimp.com/developer/marketing/guides/access-user-data-oauth-2/) they do not provide an expiry param but it’s hard to tell whether they’re simply not adhering to the spec or whether it’s an issue with omniauth, oauth2, omniauth-oauth2 or this gem here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #7