Have IdentityManager always pass on refresh token removal notifications
ProfileOAuth2TokenService has a corner case wherein during startup, it can fire token removal notifications for accounts for which it has never previously filed a token available notification. IdentityManager currently swallows such notifications. However, as we streamline IdentityManager to be just a straight pass-through to its backing classes (crbug.com/883722), IdentityManager will no longer be able to detect this case (because it won't be maintaining any cached info from the token available notifications). This CL makes the behavioral change of having IdentityManager always pass on token removal notifications from ProfileOAuth2TokenService. The behavioral impact is that consumers of IdentityManager::Observer::OnRefreshTokenRemovedForAccount() will now see a removal notification in the corner case described above. However, all such consumers were previously consumers of ProfileOAuth2TokenService::Observer::OnRefreshTokenRevoked() before their conversion and hence were previously seeing the removal notification in this corner case. Thus, the behavioral change does not seem to have a concrete impact on consumers one way or the other. Bug: 883722 Change-Id: I131ad8dbe12d73772845fd2eb565cd3477779c36 Reviewed-on: https://chromium-review.googlesource.com/1225878Reviewed-by:Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#592794}
Showing
Please register or sign in to comment