We currently have 2 servers that simultaneously access the same account. They use different refresh tokens though and we never had an issue for over a year.
However, we'll soon be implementing a solution that requires 10 servers to simultaneously access accounts that share the same refresh token. I'll run a test to see if this works without having to share the access token. I'll report my findings here. Oliver On Thursday, February 27, 2014 8:58:06 PM UTC, HK wrote: > > Oliver, > > Sorry for the delay. I have not tried to set this up, but looking into it > some more and reading the OAuth 2.0 RFC<http://tools.ietf.org/html/rfc6749>, > I came to the conclusion that it isn't safe to assume that you can have > multiple valid access token and refresh tokens at any given time, even a > very limited number. So I'm going to maintain one set of tokens in a shared > SQL database table. Whether this is the best way to do it, I can't say, but > for our environment, it seems to be the better choice. > > Hans > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
