Kyle, is there any reason that we couldn't just eliminate CryptAuthAccessTokenFetcher(Impl) entirely, having its clients directly use PrimaryAccountAccessTokenFetcher?
No, I don't believe there's any reason we couldn't do that. The CryptAuthAccessTokenFetcher class was created ~5 years ago, so AFAIK PrimaryAccountAccessTokenFetcher was unavailable when it was created.
We just haven't gotten around to it yet since it works as-is and would require a refactor which we haven't prioritized. If you'd like to take a crack at it, please feel free! :)
Comment 1 by blundell@chromium.org
, Feb 6 2018Components: Internals>Services>Identity
Status: Available (was: Untriaged)