access token not getting refreshed after updating to V201502

[Seth]

Hey,

I just updated my app to V201502 a few days ago and now the access token no longer gets automatically refreshed. Any idea why that might be?

Thanks,

Seth

[Danial Klimkin]

Hello Seth,

What client library are you using?

-Danial, AdWords API Team.

[Seth]

google-adwords-api (0.14.2)

[Seth]

Ruby

[Danial Klimkin]

Please make sure you don't have access_token specified in the adwords_api.yml, just the refresh_token.

-Danial.

[Seth]

Ok thanks!

[Nadine Sundquist (AdWords API Team)]

Hi Seth,

I would recommend checking to make sure that your refresh token has not become invalid. Here are a few reasons why a refresh token may become invalid:

• The refresh token expires after being unused for 6 months.
• The refresh token limit per user per application has been reached. The current limit is listed in the OAuth 2.0 guide.
• The user has revoked access.

Cheers,

Nadine, AdWords API Team

[Seth]

now im getting this error AuthenticationError.OAUTH_TOKEN_HEADER_INVALID

[Seth]

Im working with a brand new refresh token. My application runs until the token expires and then i get this error `AuthenticationError.OAUTH_TOKEN_INVALID`. I then need to get new tokens from oauth playground.

[Danial Klimkin]

Hi Seth,

Did you make any changes to the configuration file between versions? There were no auth-affecting changes so the new version should work the same way with the same configuration file.

Make sure you still have 

  :oauth2_client_id

  :oauth2_client_secret

  :oauth2_token

    :refresh_token

defined.

Note, refresh token is a subkey of oauth2_token.

-Danial, AdWords API Team.

[Seth]

Yeah, thats all the same. But until now i always had the `refresh_token` as well. When did that change?

[Danial Klimkin]

Yes, you do need refresh_token on the config.

Please let me also now the ads-common and signet gem versions you are using.

-Danial.

[Seth]

google-ads-common (0.9.8)
signet (0.6.0)

[Seth]

Sorry i meant `access_token`, I always had both the `access_token` and `refresh_token`. I also just created a sample app with a fresh install of everything and its not working without the `access_token`

[Danial Klimkin]

I'll try to create a fresh setup and reproduce.

In the meanwhile, can you describe the original issue in more detail? Did some of the request succeed but then stop?

-Danial.

[Seth]

Yes, so when I go on OAuth 2.0 Playground and get new tokens my app runs (using both tokens in my yml file).  However, once the token expires it stops working and i'm getting the AuthenticationError.OAUTH_TOKEN_INVALID error.

Not sure if this makes a difference, but, I am keeping the `adwords_api.yml` in my apps root directory and passing as a param like this `AdwordsApi::Api.new("./adwords_api.yml")`.

[Danial Klimkin]

Do you also have :issued_at: defined? What is its value?

-Danial.

[Seth]

right now its blank

[Danial Klimkin]

Try setting it to the timestamp of token generation, or to an old date. Eg.:

    :oauth2_token:

    :access_token: ****

    :refresh_token: ****

    :issued_at: 2014-05-13 14:29:18.110177979 +04:00

-Danial.

[Seth]

Ok now im getting `rescue in refresh_token!': OAuth2 token refresh failed (AdsCommon::Errors::AuthError)

[Danial Klimkin]

Hello Seth,

I suggest re-generating your refresh token. From the error below it looks like the refresh is triggered correctly but the token was not valid.

-Danial.

[Seth]

Ok so i refreshed and im getting the same error. However, when I change `issued_at` back to blank the request works.

[Danial Klimkin]

Interesting. Thanks for reporting. I'll check if something has changed with the new signet version.

-Danial.

[Seth]

Ok thanks, let me know? Did you get your sample app working?

[Danial Klimkin]

Sample app works for me (though I had to get a new refresh token as well).

I understand you could get requests to succeed, so the immediate problem was resolved for you?

-Danial.

[Seth]

Not really, my app takes a few hours to run. I can only get the requests to work when i do a manual refresh, which i cant do while the app is running.

[Seth]

Now that you got a new `refresh_token`, does your app refresh the `access_token` automatically or do you need to do that manually as well?

[Danial Klimkin]

This is the expected behavior. Does it work for you now automatically?

-Danial.

[Seth]

Yeah, I got it working.