Details
-
Type: Improvement
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.2
-
Fix Version/s: All Time Backlog
-
Component/s: Admax Deployment Service, Data Summarization
-
Labels:None
-
Sprint:High Priority
Description
GoogleAdWordsAPI currently stores an auth token in sesystem.googleAuthToken. When we change the username/pass in licensing.properties, the auth token should automatically be refreshed.
Currently, the auth token is not refreshed. In the case of a password change, the auth token gets expired and we get authorization errors (such as AML-1628).
If we're changing to a completely new username/password, the existing auth token does not expire or become invalid. The existing auth token can continue to be used, unnoticed, until we see some side effect (such as on June 6 when we couldn't add a budget for NTT (see "NTT Ready?" email thread)).