The API used by this is:
  * PO2TS::UpdateCredentials()
  * PO2TS::LoadCredentials()

The first one can be replaced with AccountsMutator::AddOrUpdateAccount(), but there are at the moment no mappings for LoadCredentials().

I remember, though, that you initially added AccountsMutator::LoadFromDisk() in crrev.com/c/1333775, which then got removed in crrev.com/c/1374985, but I can't find any comment explaining why it got removed neither on that second CL nor on crbug.com/740117.

Reading a comment in the first CL, I see this comment right before landing:

> > > chrome/browser/supervised_user/supervised_user_service.cc
> > The supervised users are pretty much dead on desktop and theoretically soon to be dead on ChromeOS too (though this discussion has been on-going for more than a year).  Again this is a case where the SigninManager is not used I think.
> > 
> Thanks for the analysis! I agree with all of it. I think that eventually we should not have this method, but at this time we need it. I added a comment saying that it should not be called in normal flow. WDYT?

...where you all seem to acknowledge this API would be needed for now, even if the "supervised user is pretty much dead on desktop".

What is the current status? If this API is not needed anymore, could you clarify how a class like this one is meant to be migrated away from PO2TS?

Thanks in advance!

Hi Mario,

Thank you for flagging this! I got a little overeager on crrev.com/c/1374985 and simply forgot that LoadCredentials() still had some production usage even with what that CL was removing. I'm following up on  crbug.com/922019  now.

Nice! Thanks for following up on this one, I was starting to think I was missing something obvious here :-).

CL here: https://chromium-review.googlesource.com/c/chromium/src/+/1415410
(pending on a legacy API for LoadCredentials() to be available)