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

Compliance fix for tokens that never expire (e.g. Mailchimp) #509

Open
corradio opened this issue Jan 16, 2023 · 0 comments
Open

Compliance fix for tokens that never expire (e.g. Mailchimp) #509

corradio opened this issue Jan 16, 2023 · 0 comments

Comments

@corradio
Copy link

corradio commented Jan 16, 2023

Hello,

I've encountered an issue when integrating with Mailchimp, as it turns out mailchimp tokens never expire.
A compliance fix is available here. It is an access_token_response hook, where the expired_in value is set to 3600 instead of 0. The consequence is that when my app is authorized and a token is fetched, I can use that token for 3600 seconds.

The problem is that I'd like to store and use this token once the arbitrary 3600 seconds have passed. Currently, there doesn't seem to be a way around that. Has anyone had the same issue?

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