Hey Jimmy, I have similar problems in my system, but I understand that CC is changing the refresh token each time due to a secuirity measure. But I have a question here, let's say there are multiple places in app where CC integration is required with the same account. If my users authenticate for multiple places, only one of them would work because only 1 pair of access/refresh tokens will be valid. I can still work around this problem by storing one pair of access/refresh token in one place, and using that in all places in app. BUT, tell me this, let's say 9 o clock, the acess token is going to expire. And 9:01, 3-4 places in my code pick up the refresh token to generate new access token, and then make some API call to push data in CC. Some of those requests will fail, right? Because one of them will generate a new refresh token and if the other requests are running parellel, they will pick up the old refresh token from the db in that few 100 ms, and they would fail, rigth?
... View more
I am a developer for poptin.com and I am working on an integration with Constant Contact. I am using OAuth to authenticate with your platform. But there seems to be an issue, when the user authorizes a second time, the tokens that were issued on the first time become invalid. This doesn't happen with OAuth on other platforms. Is this a security thing? In Poptin, the client can choose to connect the Constant Contact integration in a few places, but as soon as they will try to authenticate and connect in multiple places, old integrations will stop working. How to work around this? Is there a way there to make the authentication work with multiple tokens?
... View more